zelo72
/
documentation
mirror of https://github.com/mastodon/documentation
1
0
Fork 0
Code Issues 6 Releases Wiki Activity

Merge pull request #287 from zunda/no-direct-rake-run 

Remove the procedure to run `rake secret` outside the container
This commit is contained in:
Eugen Rochko 2017-06-03 15:16:17 +02:00 committed by GitHub
parent 0d9ec12d86 58d6dcb46a
commit 575a9492c8
1 changed files with 3 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
Running-Mastodon/Docker-Guide.md
View File

@ -21,9 +21,8 @@ Then, you need to fill in the `.env.production` file:
Do NOT change the `REDIS_*` or `DB_*` settings when running with the default docker configurations. Do NOT change the `REDIS_*` or `DB_*` settings when running with the default docker configurations.
You will need to fill in, at least: `LOCAL_DOMAIN`, `LOCAL_HTTPS`, `PAPERCLIP_SECRET`, `SECRET_KEY_BASE`, `OTP_SECRET`, and the `SMTP_*` settings. To generate the `PAPERCLIP_SECRET`, `SECRET_KEY_BASE`, and `OTP_SECRET`, you may use: You will need to fill in, at least: `LOCAL_DOMAIN`, `LOCAL_HTTPS`, and the `SMTP_*` settings.
rake secret
## Building the app ## Building the app
@ -31,9 +30,9 @@ Before running the first time, you need to build the images:
docker-compose build docker-compose build
docker-compose run --rm web rake secret Now the image can be used to generate secrets. Run the command below for each of `PAPERCLIP_SECRET`, `SECRET_KEY_BASE`, and `OTP_SECRET` then copy the results into the `.env.production` file:
Do this once for each of those keys, and copy the result into the `.env.production` file in the appropriate field. docker-compose run --rm web rake secret
Then you should run the `db:migrate` command to create the database, or migrate it from an older release: Then you should run the `db:migrate` command to create the database, or migrate it from an older release: