Django REST Framework playground. A fun place to play around with DRF. Check out the project's documentation.

Here is an overview of how to get the project running (from scratch) on a new dev environment.

1. Follow the steps below EXACTLY as written for best results.
2. Clone the project.
3. Install the prerequisites (see the "Prerequisites" section below).
   • Note: For OS X environments, you should be able to simply run the following to complete this step:

cd <path_to_cloned_repo>
cd scripts
bash workspace.update.osx.sh

4. Follow the instructions in the "One-time setup" section (below).
   • Create the virtualenv.
   • Create the database.
   • Migrate the DB, create a superuser, and run the server.
5. Follow the instructions in the "Running the app" section (below).
   • Run the tests.
   • Run the app server.
   • Manually explore app in your browser.
6. Begin exploring the source code in your IDE.
   • Make source code changes.
   • Run the tests.
   • Run the app server.
   • Manually explore/test the app in your browser.

• virtualenv
  • e.g. "pip install virtualenv"
• postgresql
  • e.g. "brew install postgresql" on OS X
• graphviz
  • e.g. "brew install graphviz" on OS X
  • This is used by some of the examples' endpoints and their tests.
• (Recommended) PyCharm or IntelliJ IDEA (with the Python plugin)
  • The project includes PyCharm/IDEA Run Configurations that allow many of the steps below to be executed directly from the IDE.
  • There are free editions of these tools available, so there is no good reason to suffer with Eclipse.
  • You'll probably want to install the appropriate plugins for enhanced IDE functionality. I recommend:
    • Python (if you are using IntelliJ rather than PyCharm)
    • Bash
    • Markdown
  • Note: If you get a 'Django facet' warning from a free edition of the IDE, it is safe to ignore it.

Notes:

• Bash scripts for many common operations are located in the /scripts/ folder under the project root. All of them are designed to be run from the directory they are located in.
• The /scripts/init.sh file can be modified to customize the location and name of the virtualenv.
• Warning: If you didn't install the prerequisites above, some of the scripts and run configurations may throw cryptic errors.
• IntelliJ Shared Run Configurations are also available for many of those Bash scripts.
• The examples and Bash scripts were created for Mac (OS X) development. Alterations or equivalent implementations may be needed for use on Windows or Linux.
• The subsequent examples all assume the following paths are set correctly as environment variables. However, these env variables are not required by the app itself, they are merely intended to make the CLI examples in this readme more easily customizable.

REPO_PATH=~/dev/github/Justin-W/drfunland/drfunland
SCRIPTS_PATH=${REPO_PATH}/scripts

Create and configure a virtualenv:

cd ${SCRIPTS_PATH}
bash venv.update.hard.sh

cd ${SCRIPTS_PATH}
bash venv.update.sh

Note: Make sure your postgresql server is installed and running. e.g.:

postgres -D /usr/local/var/postgres

Then create the app's (empty) DB:

createdb drfunapp

Note: This is only necessary when creating a new git repo, not if you are cloning an existing one.

cd ${REPO_PATH}
git init
git remote add origin git@github.com:Justin-W/drfunland.git

cd ${SCRIPTS_PATH} && source venv.activate.sh
#or: source ${VENV_PATH}/bin/activate

cd ${REPO_PATH}

#apply DB migrations
python drfunapp/manage.py migrate

#insert a superuser in the DB
python drfunapp/manage.py createsuperuser

#run the server
python drfunapp/manage.py runserver

Run the project's test suite:

cd ${SCRIPTS_PATH}
bash fab.test.sh

Start the project's server:

cd ${SCRIPTS_PATH}
bash fab.serve.sh

Assumes the app's server is already running (as described above):

#once running, access the app at:
open http://127.0.0.1:8000/api/v1/
open http://127.0.0.1:8000/admin/

This app contains optional (and disabled by default) functionality related to Heroku cloud server deployment. You should SKIP all of the Heroku-related steps below unless you are actually going to deploy to Heroku.

Note: The following are only needed if you plan on deploying to heroku.

• redis
• travis cli
• heroku toolbelt
  • e.g. "brew install heroku-toolbelt" on OS X

Note: you'll need to uncomment the "#deploy:" section of the '.travis.yml' file to enable automatic Heroku deployment.

By default the included fabfile will setup three environments (as separate git remotes):

• dev -- The bleeding edge of development
• qa -- For quality assurance testing
• prod -- For the live application

Create these servers on Heroku with:

cd ${REPO_PATH}
source ${VENV_PATH}/bin/activate
fab init

Deployment is handled via Travis. When builds pass Travis will automatically deploy that branch to Heroku. Enable this with:

travis encrypt $(heroku auth:token) --add deploy.api_key