From 3b850455989278f214d67dd16a0b234e630112b4 Mon Sep 17 00:00:00 2001 From: Ben Fritsch Date: Thu, 2 May 2019 10:09:14 -0400 Subject: [PATCH] fix small typos --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index dda275c..41d5d84 100644 --- a/README.md +++ b/README.md @@ -178,18 +178,18 @@ Before we push the code up, let's set the config vars (or we'll see errors!) You can remind yourself what environment variables we need by looking at your `heroku.py` file, but to get this project ready to run, you can use the CLI `heroku config` command. ``` -heroku config ALLOWED_HOSTS=your-app-name.com -heroku config DJANGO_SETTINGS_MODULE=dynowiki.settings.heroku +heroku config:set ALLOWED_HOSTS=your-app-name.herokuapp.com +heroku config:set DJANGO_SETTINGS_MODULE=dynowiki.settings.heroku ``` For the SECRET_KEY, you'll need to generate a new secret. For this demo, it doesn't matter what it is - it's great to use a secure hash generator, or a password manager's generator. Just be sure to keep this value secure, don't reuse it, and NEVER check it into source code! ``` -heroku config SECRET_KEY=YOURSECUREGENERATEDPASSWORD +heroku config:set SECRET_KEY=YOURSECUREGENERATEDPASSWORD ``` Lastly, Heroku will automatically detect the number of concurrent processes you want to run on each dyno. Depending on the resource usage of your process, this can make each dyno handle more requests more quickly - but for now, let's stick to one process. ``` -heroku config WEB_CONCURRENCY=1 +heroku config:set WEB_CONCURRENCY=1 ``` ## Heroku Deploy