This is a simplified, but fairly thorough, set of scripts and configuration to enable Heroku Release Phase for Rails apps.
Further, this particular set up plays nicely with Heroku Review Apps in that the release
phase script will:
- Fail, loudly, if the DB does not yet exist.
- Load the DB schema if the current schema version (as determined by
bin/rails db:version
) is0
. - Run DB migrations otherwise.
For a "normal" app that usually means it will run the DB migrations.
For a Review App, on the first deploy the release
phase will bin/rails db:schema:load
.
And then the postdeploy
script will seed data.
During subsequent deploys to the Review App, the release
phase will bin/rails db:migrate
.
Also, for those asking about running
heroku restart
. I'm not sure that's strictly necessary. I did run into problems when running tasks that relied on the new DB schema (eg,%w[db:migrate db:seed]
). There's no problem if you run them as discreterake
commands, since the application code is reloaded, but in the same task, you'll need something like