...
There are ways to set up command-line access to papertrail logs too. https://github.com/papertrail/papertrail-heroku-plugin https://github.com/papertrail/papertrail-cli
Even without papertrail you can use heroku cli
heroku logs -a scihist-digicoll-productionto look at running trail of current heroku logs, but the display isn’t nearly as nice as papertrail, and includes more noise that papertrail filters out.
...
Look at release history with heroku CLI:
heroku releases -a scihist-digicoll-production
Failed releases will be in red. With the id from the left-most column, you can look at specific log output (mainly of our custom release phase) for the failed or successful release, eg:
heroku releases:output v323 -a scihist-digicoll-production
You can also see some limited release status info in the Web GUI on the Activity tab.
...
Login to searchstax
Use shared credentials stored in our credential spot on the P:\ drive
Click on the instance you want to restart (
scihist_digicoll(production), orscihist-digicoll-staging)At bottom of page there is a single node listed (our plan only has one node), you can click “stop solr”, and then “Start solr”
...
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.
In heroku config vars on section of the heroku dashboard settings tab, just set LOGINS_DISABLED to true.
...
Restore postgres database from backups
See separate page.