Skip to content

Instantly share code, notes, and snippets.

@dustinmm80

dustinmm80/panel_outline_2_18.md

Last active August 29, 2015 13:56
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save dustinmm80/9004362 to your computer and use it in GitHub Desktop.
Save dustinmm80/9004362 to your computer and use it in GitHub Desktop.
Download ZIP
Boston DevOps application configuration panel outline for 2/18
Raw
panel_outline_2_18.md

Outline

Application configuration

  • Do you use config files for your app, or do you have a distributed solution? (etcd, serf, etc)

    If config files:

    • How do you set them up to work in multiple environments?
    • How are they different for developer machines?

    If distributed:

    • Which solution are you using and why?
    • Why did you choose to use it instead of config files?
    • How difficult is it to set up and maintain?

Security

  • How do you manage secrets for your configuration? (passwords, API keys, etc)
  • How do you manage secret files?
  • Do you use user/pass for different internal apps, or another solution?

State

  • Is your configuration static or dynamic?
  • How do your deploys take changed configuration into account?
  • How do you monitor whether a config change gives the desired result?
  • How do you manage the state of your configuration across environments (dev, prod)?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment