Skip to content

Instantly share code, notes, and snippets.

@sunilake

sunilake/devops_checklist.md

Forked from jamesob/devops_checklist.md
Created August 3, 2018 13:36
Show Gist options
  • Star 1 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save sunilake/b8da47b2ec194d0bbbc9879c289d929f to your computer and use it in GitHub Desktop.
Save sunilake/b8da47b2ec194d0bbbc9879c289d929f to your computer and use it in GitHub Desktop.
Download ZIP
DevOps checklist
Raw
devops_checklist.md

Security

  • no credentials kept in codebase
    • use consul/zookeeper/etc., then have code load credentials from environment variables
  • using a bastion box to safeguard access to servers
    • in conjunction with, e.g., AWS security groups

Development

  • master is always deployable
    • this means that proposed changesets are always tested prior to being merged to master
    • this probably means that a CI solution must be implemented
  • infrastructure topology is replicated faithfully in QA/staging
    • this means that if you have, e.g., separate database servers in PROD, you should have them separated on QA as well
    • a little much to ask for dev environments, but bonus points if possible
  • deploys happen automatically on merge to master

Montoring

  • logging is centralized
  • metrics-per-feature are collected to verify live functionality
  • stacktrace aggregation (e.g. Sentry) is in place
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment