From 64a1c834b2bf5de890a31a236353a6b9f39056e4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?wxcaf=C3=A9?= Date: Thu, 27 Apr 2017 10:56:41 +0200 Subject: [PATCH] Docker-guide consistency --- Running-Mastodon/Docker-Guide.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Running-Mastodon/Docker-Guide.md b/Running-Mastodon/Docker-Guide.md index 695cccb7..09c93b12 100644 --- a/Running-Mastodon/Docker-Guide.md +++ b/Running-Mastodon/Docker-Guide.md @@ -74,6 +74,6 @@ This approach makes updating to the latest version a real breeze. 3. `git checkout TAG_NAME` to use the tag code. (If you have committed changes, use `git merge TAG_NAME` instead, though this isn't likely.) 4. Only if you ran `git stash`, now run `git stash pop` to redo your changes to `docker-compose.yml`. Double check the contents of this file. 5. `docker-compose build` to compile the Docker image out of the changed source files. -6. (optional) `docker-compose run --rm web rails db:migrate` to perform database migrations. Does nothing if your database is up to date. -7. (optional) `docker-compose run --rm web rails assets:precompile` to compile new JS and CSS assets. +6. (optional) `docker-compose run --rm web rake db:migrate` to perform database migrations. Does nothing if your database is up to date. +7. (optional) `docker-compose run --rm web rake assets:precompile` to compile new JS and CSS assets. 8. `docker-compose up -d` to re-create (restart) containers and pick up the changes.