...
In heroku CLI , run heroku maintenance:on -a scihist-digicoll-production and heroku maintenance:off -a scihist-digicoll-production
(Note: Right now, this is just a generic heroku maintenance message. It is possible to customize/brand this page, we may get to that eventually. This uses a customized maintenance page in an S3 bucket, as stored in heroku config var MAINTENANCE_PAGE_URL per instructions at https://githubdevcenter.heroku.com/sciencehistory/scihist_digicoll/issues/1201 )articles/maintenance-mode#customizing-your-maintenance-page Note that S3 needs to be there, if it’s missing, may get a blank maintenance page. There seems to be no way to switch back to heroku default maintenance page, per possible heroku bug).
Disable staff logins
We can effectively make the app “read-only” but still available to the public by disabling staff logins. So we don’t have a public facing outage, but if we’re dealing with some kind of data corruption issue we’re trying to diagnose, we might want to ‘freeze’ staff out.
...