Getting started with environment configuration
It is rarely the thing that gets a project approved, and often the thing that decides how it goes. A short on-ramp to environment configuration for teams who have not touched it before.
The question is rarely whether something can be built, but what it costs to keep running afterwards. The practical test is whether someone new to the project could tell, in a minute, that it had been handled.
What is actually at stake
Secrets belong in the environment, never in the repository. There is a version of this that is over-engineered, and it is worth avoiding. The practical test is whether someone new to the project could tell, in a minute, that it had been handled.
Your first week
- Find out what is already in place
- Development and production should differ only in configuration
- Change one thing and measure it
Document every variable a new developer needs. The cost of getting this wrong is rarely visible on the day it happens. Budget a little time for it every quarter and it never becomes a project of its own.
How to tell if yours is fine
Most development decisions are really maintenance decisions wearing a different hat. Three things worth confirming about environment configuration before you move on:
- Someone can say what the current setup is without going to look
- Development and production should differ only in configuration — and you know whether that is true here
- There is a way to tell whether the last change to this helped
If any of that sounds like a description of your current setup, it is fixable.