Skip to content

Add info how to handle deploy:migrate error at the first deploy to the README #227

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Add info how to handle deploy:migrate error at the first deploy to the README #227

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1130437
Add info how to handle deploy:migrate error at the first deploy to th…
vifreefly Nov 22, 2018
1ce690b
Fix example from db:schema:load to db:setup
vifreefly Nov 22, 2018
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
4 changes: 4 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:setup`. Then try deploy again.

## Contributing

1. Fork it
Expand Down