5 ms·
Cannot upvote this highly enough. For old tech stacks we've had to maintain meticulous notes with setup and maintenance steps. They're very error prone and req
by leonroy 9y ago
Cannot upvote this highly enough.
For old tech stacks we've had to maintain meticulous notes with setup and maintenance steps. They're very error prone and require constant upkeep to keep our build notes up to date.
With our new tech stack where we're (currently) using Docker and a BASH deployment script it's a breath of fresh air. We just keep our Dockerfile and setup scripts in Git. The script tracks the app version and is self documenting. We of course know it's always going to be correct because our CI server would complain if it wasn't.
The best part of it is that the ridiculously detailed document we used to have to maintain would take as much time as our automated strategy so in engineering resource the cost difference hasn't been very much at all.
- reacweb 9y agoA good (short) script can be a better documentation and at the same time be provably correct (just run it).
- dboreham 9y agoDeployment scripts existed before Docker.
- reacweb 9y agoYes, but docker has created an incentive to publish them. When I want to install something, I search for a docker image that has it preinstalled and I read the dockerfile. I can choose either to use the docker image or to perform the installation globally on my main system. And, by the way, I have learned the installation procedure.