Production Ready

[noisecapella]

Off the top of my head this should include:

• [x] choose URL and configure DNS
• [x] Heroku and the build pipeline
• [x] Cybersource credentials
• [x] Setting up Sentry
• [x] Mail monitoring

[blarghmatey]

This is the list from when we did this for Micromasters:

"Production readiness" checklists

• [x] Move to production dyno
• [x] Move db to production db
• [x] Performance Monitoring
• [x] Production error monitoring
• [x] Mail Monitoring

  Required features:

• [x] Does it support configuration via environment variables?
• [x] Does it support configuration via flatfile (e.g. YAML)?
• [x] Does it have a sane default configuration (e.g. as close to a realistic production configuration as possible)?
• [x] Does it run on parallel HTTP workers? (e.g. uWSGI, Gunicorn)?
• [x] Does it log to standard out/error?
• [x] Does it log to syslog?
• [x] Can it send stack trace emails to a configurable email list?
• [x] Does it have configurable log levels (e.g. DEBUG, ERROR, WARNING, INFO)?
• [x] Does it have a test suite which measures code coverage?
• [x] Does it have a status route (which requires a secret token) that can be used for health checking by a monitoring service?
• [x] Does the health check validate that each service the app depends on is reachable (e.g. databases, caching, external APIs when necessary)?
• [x] Does the health check return a response body with the availability information above in a machine-readable format in all cases?
• [x] Does the health check return a 500 status code when any component in the health check is detected to be failing?

Required documentation/service infrastructure:

• [x] Does it have continuous integration builds which run the full test suite?
• [x] Does it have an automated continuous delivery to a development environment?
• [x] Does it have a documented release process?
• [x] Does it's release process include staging and production builds, where staging builds are promoted to production?
• [x] Does it's release process require that code changes be "signed off" as working on staging before being promoted to production?
• [x] Does it have application/resource monitoring in production (e.g. New Relic agent, Zenoss SNMP)?
• [x] Does it have service availability monitoring in production (e.g. periodic health checks with Zenoss or New Relic)?
• [x] Does it have automated, periodically generated, fully restorable backups for each non-ephemeral data store in production?

(From https://github.com/mitodl/handbook/blob/master/production-ready.md)

[pdpinch]

No elastic search, I believe, in this app.

No need for load testing, I think.