I had an upgrade on a 2-container install go sideways this morning. Bootstrapping a new container migrated the database into a broken state (perhaps it wouldn’t have if I’d used
SKIP_POST_DEPLOYMENT_MIGRATIONS=1, but that’s another issue), so that the running container got the “oops, this site is broken” message.
That much is expected, but my monitor is checking
/srv/status and it merrily returns an OK even when rails is pretty broken.
Is this a bug? I really want my monitors to know if there is a problem, should I instead be pulling something else like
/about.json (for sites that don’t require login).