Skip to content
This repository was archived by the owner on May 20, 2021. It is now read-only.

fix small typos #2

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

fix small typos #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down