Deployment errors if my postgres app has stopped running - what should I do?

When I do a new deploy of my app, it errors if the connected postgres app has stopped, because the release_command is bin/rails db:migrate.

Sometimes, if my site hasn’t been visited recently, the postgres app’s machines become stopped. If a deploy is then triggered (e.g. via a Github Action I have), it fails.

I’m wondering how to handle this… Should I
a) Try to start the postgres app machines as part of the release_command? Is that even possible?
b) Prevent the postgres app machines from stopping? Is that possible? Is there a setting similar to min_machines_running?
c) Try something else?

Any advice much appreciated!

Looks like a known bug:

It should auto-start when something tries to connect, but if that’s not working you can turn it off


This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.