No description
Find a file
Zane Adickes b6b6ff0938 Move Models
Created models for all move related models and added build steps for
each
2015-04-09 00:45:23 -04:00
assets initial commit 2014-12-04 11:11:46 +00:00
config Squashed migrations and cleaned up config/settings 2015-04-08 09:57:29 -04:00
data Move Models 2015-04-09 00:45:23 -04:00
hits initial commit 2014-12-04 11:11:46 +00:00
pokemon remove xml for now 2014-12-15 10:13:52 +00:00
pokemon_v2 Move Models 2015-04-09 00:45:23 -04:00
templates initial commit 2014-12-04 11:11:46 +00:00
.gitignore initial commit 2014-12-04 11:11:46 +00:00
CONTRIBUTORS.txt initial commit 2014-12-04 11:11:46 +00:00
LICENSE.rst initial commit 2014-12-04 11:11:46 +00:00
Makefile remove xml for now 2014-12-15 10:13:52 +00:00
manage.py initial commit 2014-12-04 11:11:46 +00:00
README.md code 2014-12-05 12:32:36 +00:00
requirements.txt remove xml for now 2014-12-15 10:13:52 +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. 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

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!