No description
Find a file
2016-02-13 02:36:09 +01:00
assets delete pikachu image 2016-01-09 11:10:42 -05:00
config reorganiztion and clean up. 2016-01-09 10:55:39 -05:00
data Merge pull request #81 from zaneadix/new-ui 2016-01-31 12:03:26 +00:00
hits Update migrations to allow correct upgrade path 2016-01-31 12:24:53 +00:00
pokemon still need to re-organize v2 docs and work on doc navigation 2016-01-07 08:20:10 -05:00
pokemon_v2 Fixed type info in the docs 2016-02-13 02:36:09 +01:00
templates reorganiztion and clean up. 2016-01-09 10:55:39 -05:00
.gitignore new ui code in angular 2015-12-30 08:22:15 -05:00
CONTRIBUTORS.txt new ui code in angular 2015-12-30 08:22:15 -05:00
gulpfile.js home page try it out. contributors. started docs. 2016-01-01 16:48:41 -05:00
LICENSE.rst initial commit 2014-12-04 11:11:46 +00:00
Makefile merge with what @phalt has done so far 2015-09-05 22:10:13 -04:00
manage.py initial commit 2014-12-04 11:11:46 +00:00
package.json home page try it out. contributors. started docs. 2016-01-01 16:48:41 -05:00
README.md avoid starimports readme. list of functions moved 2015-12-07 21:42:07 +01:00
requirements.txt ui using django templates 2016-01-06 17:10:05 -05:00

PokeAPI

A RESTful API for Pokemon

LICENSE: BSD

http://pokeapi.co

DEPRECATION

Quite a lot of data is missing from the V1 API.

As of January 2015, no new data will be added to the v1 API, you will have to use the V2 API instead. This is part of an ongoing deprecation of the v1 API.

See This blog post for more information.

Setup

  • Download this source code into a working directory.

  • Install the requirements using pip:

$ make install

This will install all the required packages and libraries for using PokeAPI

  • Set up the local developer environment using the following command:
$ make setup
  • Run the server using the following command::
$ make serve

Visit localhost:8000 to see the running website!

If you ever need to wipe the database use this command:

$ make wipe_db

V1 Database setup

Start Django shell

$ python manage.py shell --settings=config.local

import build functions

$ from data.v1.build import *

run the functions in order to populate v1 tables

$ build_pokes()
$ build_abilities()
$ build moves()
etc...

V2 Database setup

Start Django shell

$ python manage.py shell --settings=config.local

run the build script with

$ from data.v2.build import build_all
$ build_all()

Each time the build script is run it will iterate over each table in the database, wipe it and rewrite each row using the data found in data/v2/csv. When building against sqlite we've heard it can take a ridiculously long time to finish building out the database. In this case you can set up just the portions of the db that you need.

$ from data.v2.build import *
$ build_languages()
$ build_abilities()
...

Heres a list of the data building functions

  • build_languages()
  • build_regions()
  • build_generations()
  • build_versions()
  • build_stats()
  • build_damage_classes()
  • build_abilities()
  • build_characteristics()
  • build_egg_groups()
  • build_growth_rates()
  • build_items()
  • build_types()
  • build_contests()
  • build_moves()
  • build_berries()
  • build_natures()
  • build_genders()
  • build_experiences()
  • build_machines()
  • build_evolutions()
  • build_pokedexes()
  • build_locations()
  • build_pokemons()
  • build_encounters()
  • build_pal_parks()

Contributing

All contributions are welcome: bug fixes, data contributions, recommendations.

Please see the issues on GitHub before you submit a pull request or raise an issue, someone else might have beat you to it.

To contribute to this repository:

git clone git@github.com:<YOUR_USERNAME>/pokeapi.git
  • Create a new branch with a descriptive name:
git checkout -b my_new_branch
  • Write some code, fix something, and add a test to prove that it works. No pull request will be accepted without tests passing, or without new tests if new features are added.

  • Commit your code and push it to GitHub

  • Open a new pull request and describe the changes you have made.

  • We'll accept your changes after review.

Simple!