From 8c156e4830d3860dc6c820674c98a04884add443 Mon Sep 17 00:00:00 2001 From: Sylvain Date: Wed, 15 Nov 2017 10:20:23 +0100 Subject: [PATCH] fix docker-compose deploy instructions --- CHANGELOG.md | 4 ++++ docker/README.md | 5 +++-- 2 files changed, 7 insertions(+), 2 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 66f339975..ebab35cd0 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,9 @@ # Changelog Fab Manager +## next release + +- Fixed deploy instructions with docker-compose + ## v2.6.0 2017 November 13 - Additional button to delete a slot, allowing to delete slots masked by others diff --git a/docker/README.md b/docker/README.md index 16ba5a62b..00d1a4a42 100644 --- a/docker/README.md +++ b/docker/README.md @@ -196,7 +196,8 @@ docker-compose pull ```bash docker-compose run --rm fabmanager bundle exec rake db:create # create the database docker-compose run --rm fabmanager bundle exec rake db:migrate # run all the migrations -docker-compose run --rm -e ADMIN_EMAIL=xxx ADMIN_PASSWORD=xxx fabmanager bundle exec rake db:seed # seed the database +# replace xxx with your default admin email/password +docker-compose run --rm -e ADMIN_EMAIL=xxx -e ADMIN_PASSWORD=xxx fabmanager bundle exec rake db:seed # seed the database ``` ### build assets @@ -326,4 +327,4 @@ You can check that all containers are running with `docker ps`. Yes, indeed. It's the default behaviour as `docker-compose pull` command will fetch the latest versions of the docker images. Be sure to run all the specific commands listed in the [CHANGELOG](https://github.com/LaCasemate/fab-manager/blob/master/CHANGELOG.md) between your actual -and the new version in sequential order. (Example: to update from 2.4.0 to 2.4.3, you will run the specific commands for the 2.4.1, then for the 2.4.2 and then for the 2.4.3). \ No newline at end of file +and the new version in sequential order. (Example: to update from 2.4.0 to 2.4.3, you will run the specific commands for the 2.4.1, then for the 2.4.2 and then for the 2.4.3).