Secure Redis via SSL

This also adds the use of the Heroku Multi Buildpack which installs multiple buildpacks as defined in .buildpacks (in order)

.buildpacks

@@ -0,0 +1,3 @@
+https://github.com/heroku/heroku-buildpack-redis.git
+https://github.com/heroku/heroku-buildpack-python.git
+https://github.com/heroku/heroku-buildpack-addon-wait.git

Procfile

@@ -1,7 +1,7 @@
-web: newrelic-admin run-program gunicorn atmo.wsgi:application --workers 4 --log-file -
-worker: newrelic-admin run-program python manage.py rqworker --worker-class=rq.SimpleWorker default
+web: bin/start-stunnel newrelic-admin run-program gunicorn atmo.wsgi:application --workers 4 --log-file -
+worker: bin/start-stunnel newrelic-admin run-program python manage.py rqworker --worker-class=rq.SimpleWorker default
 # django-rq doesn't support rqscheduler retry mode yet
 # so we need to use the original startup script
-scheduler: newrelic-admin run-program rqscheduler --url=$REDIS_URL
+scheduler: bin/start-stunnel newrelic-admin run-program rqscheduler --url=$REDIS_URL
 
 release: ./bin/pre_deploy

README.md

@@ -90,7 +90,8 @@ Heroku Setup
 1. `heroku create`
 2. `heroku config:set DEBUG=False ALLOWED_HOSTS=<foobar>.herokuapp.com, SECRET_KEY=something_secret`
    `DATABASE_URL` gets populated by heroku once you setup a database.
-3. push to GitHub with `git push origin`
+3. Run `heroku buildpacks:set https://github.com/heroku/heroku-buildpack-multi.git` since we're using multiple Heroku buildpacks (see `.buildpacks`)
+4. Push branch to GitHub with `git push origin`, Heroku will auto-deploy to staging
 
 NewRelic Monitoring
 -------------------