Everything-as-Code: It's time to fix configurations
summary
Argues that treating configs as code removes drift and human errors and demonstrates it with the open source configu CLI, a CFG schema file and a simple JSON-backed JSON store. Builds a hello‑world Node app with three keys (greeting, subject, message template), shows schema validation rejecting an invalid regex match, uses upsert to create development, production and customer sets, exports to dotenv, and runs the app showing undefined without config and the expected greeting when configs are applied.
AI-written summary · about
chapters (11)
- 0:00intro
- 0:22preamble
- 0:45about peleg
- 1:13what we will cover
- 2:08application configuration
- 3:36challenge with configurations
- 5:33everything-as-code
- 5:54configuration-as-code (cac)
- 7:49introduction to configu
- 10:05hands-on example
- 17:44thank you!
related talks
19mConfig as Code
37mCoding Automation Lesson #1: Please Be Lazy
47mCuttlefish Easing the Pain of Configuration
27mThe code etymologist
59mEverything as a Code
24mUsing Declarative Configs for Maintainable Reproducible Code
26mYet Another Config File: introducing node.config.json
01h 02mModern .NET Configuration Practices