From f803f8f2ab29ae621f00a817ece03ed0cdd144f3 Mon Sep 17 00:00:00 2001 From: Daniel Roy Greenfeld Date: Mon, 26 Sep 2016 10:23:45 -0700 Subject: [PATCH] FAQ entry on combining multiple deployment options --- docs/deployment-with-elastic-beanstalk.rst | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/deployment-with-elastic-beanstalk.rst b/docs/deployment-with-elastic-beanstalk.rst index 5074770f..54c32fec 100644 --- a/docs/deployment-with-elastic-beanstalk.rst +++ b/docs/deployment-with-elastic-beanstalk.rst @@ -62,3 +62,8 @@ 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.