No description
Find a file
2016-03-05 12:25:50 +00:00
assets delete pikachu image 2016-01-09 11:10:42 -05:00
config final lints 2016-03-05 11:40:41 +00:00
data build script fixes 2016-03-05 12:25:50 +00:00
hits final lints 2016-03-05 11:40:41 +00:00
pokemon final lints 2016-03-05 11:40:41 +00:00
pokemon_v2 Fix migrations again 2016-03-05 12:14:10 +00:00
templates fixed broken sprites stuff 2016-03-01 22:12:18 +01:00
.gitignore new ui code in angular 2015-12-30 08:22:15 -05:00
circle.yml Linting for the entire project 2016-03-05 09:27:25 +00:00
CONTRIBUTORS.txt new ui code in angular 2015-12-30 08:22:15 -05:00
Dockerfile Changed Dockerfile over to use postgres. Adding custom config for the Dockerfile. 2016-02-29 21:05:25 -06: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 Linting for the entire project 2016-03-05 09:27:25 +00: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 Version bumps, removing whitespaces 2016-03-05 08:26:51 +00:00
requirements.txt Version bumps, removing whitespaces 2016-03-05 08:26:51 +00:00
setup.cfg do not lint node stuff 2016-03-05 11:42:58 +00:00
test-requirements.txt Linting for the entire project 2016-03-05 09:27:25 +00: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.

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()

Docker

The application can be built and run as a Docker container for easy deployments

From the root directory of the cloned repo

docker build -t pokeapi .

Run the container on host port 8000

docker run -d -p 8000:8000 pokeapi

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!