> env.production.toml
Which production env? Which datacenter? Which database cluster? &c
The deployment should take care of generating configs, they shouldn't be hardcoded or stored anywhere imho.
Which production env? Which datacenter? Which database cluster? &c
The deployment should take care of generating configs, they shouldn't be hardcoded or stored anywhere imho.
Sure deployment can generate configs but it has to take it from somwhere. So you need a database preferably with versioning and encryption. It's also nice if you know which settings are used in specific builds so you can go back and debug past production issues.
Of course for larger teams and deployments it makes sense to develop and maintain this infrastructure. But since we already have git, why not just use it.