25 ms·
> always had an script or executable that gets the environment up to date with the new version. Which means you’re writing deployment tools already. Going from
by gjulianm 4y ago
> always had an script or executable that gets the environment up to date with the new version.
Which means you’re writing deployment tools already. Going from there to an abstraction that provides the primitives you use in those scripts is a natural step.
> There were plenty of tools to manage that loop too if you didn't want to keep the information on a simple text file.
Indeed. But again, this shows how deployment tools evolve naturally from “git pull” to something more complex. It’s not complexity for the sake of it.
> Well, that's a "don't".
If only managing computers was as easy as telling people what not to do.