cookiecutter-django/docs/deployment-with-elastic-beanstalk.rst

Deployment with Elastic Beanstalk
==========================================

.. index:: Elastic Beanstalk

Warning: Experimental
---------------------

This is experimental. For the time being there will be bugs and issues. If you've never used Elastic Beanstalk before, please hold off before trying this option.

On the other hand, we need help cleaning this up. If you do have knowledge of Elastic Beanstalk, we would appreciate the help. :)

Prerequisites
-------------

* awsebcli

Instructions
-------------

If you haven't done so, create a directory of environments::

  eb init -p python3.4 MY_PROJECT_SLUG

Replace `MY_PROJECT_SLUG` with the value you entered for `project_slug`.

Once that is done, create the environment (server) where the app will run::

  eb create MY_PROJECT_SLUG
  # Note: This will eventually fail on a postgres error, because postgres doesn't exist yet

Now make sure you are in the right environment::

  eb list

If you are not in the right environment, then put yourself in the correct one::

  eb use MY_PROJECT_SLUG

TODO: Finish it::

  # Set the environment variables
  python ebsetenv.py

  # Go to EB AWS config. Create new RDS database (postgres, 9.4.9, db.t2.micro)
  # Get some coffee, this is going to take a while

  # Deploy again
  eb deploy

  # Take a look
  eb open

FAQ
-----

Why Not Use Docker on Elastic Beanstalk?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Because I didn't want to add an abstraction (Docker) on top of an abstraction (Elastic Beanstalk) on top of an abstraction (Cookiecutter Django).

Why Can't I Use Both Docker/Heroku with Elastic Beanstalk?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Because the environment variables that our Docker and Heroku setups use for PostgreSQL access is different then how Amazon RDS handles this access. At this time we're just trying to get things to work reliably with Elastic Beanstalk, and full integration will come later.