From 113043795b28de8074e6347325433337599ec9e8 Mon Sep 17 00:00:00 2001 From: Victor Afanasev Date: Thu, 22 Nov 2018 13:26:33 +0400 Subject: [PATCH 1/2] Add info how to handle deploy:migrate error at the first deploy to the README.md --- README.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/README.md b/README.md index 43ae07b..a22b926 100644 --- a/README.md +++ b/README.md @@ -113,6 +113,10 @@ set :migration_role, :app The advantage is you won't need to deploy your application to your database server, and overall a better separation of concerns. +### Handle database creation at the first deploy + +Capistrano-rails does not create database for you before calling `deploy:migrate` task (see here why: [issues/118](https://github.com/capistrano/rails/issues/118#issuecomment-440870686)). That means `cap production deploy` will fail if database is not created yet on the deploy server. If that is your case, go to the deploy server, `cd` into latest release directory with your application and create database with the required environment. Example: `RAILS_ENV=production rails db:create` or `RAILS_ENV=production rails db:schema:load`. Then try deploy again. + ## Contributing 1. Fork it From 1ce690b8fbf742331cae16bac615a49701dae83a Mon Sep 17 00:00:00 2001 From: Victor Afanasev Date: Thu, 22 Nov 2018 17:23:29 +0400 Subject: [PATCH 2/2] Fix example from db:schema:load to db:setup --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index a22b926..8b435f5 100644 --- a/README.md +++ b/README.md @@ -115,7 +115,7 @@ server, and overall a better separation of concerns. ### Handle database creation at the first deploy -Capistrano-rails does not create database for you before calling `deploy:migrate` task (see here why: [issues/118](https://github.com/capistrano/rails/issues/118#issuecomment-440870686)). That means `cap production deploy` will fail if database is not created yet on the deploy server. If that is your case, go to the deploy server, `cd` into latest release directory with your application and create database with the required environment. Example: `RAILS_ENV=production rails db:create` or `RAILS_ENV=production rails db:schema:load`. Then try deploy again. +Capistrano-rails does not create database for you before calling `deploy:migrate` task (see here why: [issues/118](https://github.com/capistrano/rails/issues/118#issuecomment-440870686)). That means `cap production deploy` will fail if database is not created yet on the deploy server. If that is your case, go to the deploy server, `cd` into latest release directory with your application and create database with the required environment. Example: `RAILS_ENV=production rails db:create` or `RAILS_ENV=production rails db:setup`. Then try deploy again. ## Contributing