Before adopting containers it wasn't unusual to SSH in and change a line of code on a broken server and restart. In fact that works fine while the company/team is really small. Unfortunately it becomes a disaster and huge liability when the team grows.
Writing a script to ssh into a bunch of machines and run a common command is the next step. That works far longer than most people acknowledge.
I pine for the old days - I really do. Things are insanely complex now and I don't like it. Unfortunately there are good reasons for the complexity.
Meh.
Containers provide solutions to the problems that someone else had. If you don't have those problems, then containers just create complexity and problems for you.
What problems do they solve? They solve, "My codebase is too big to be loaded on one machine." They solve, "I need my code to run in parallel across lots of machines." They solve, "I need to satisfy some set of regulations."
If you do not have any of those kinds of problems, DON'T USE CONTAINERS. They will complicate your life, and bring no benefit that you care about.
Writing a script to ssh into a bunch of machines and run a common command is the next step. That works far longer than most people acknowledge.
I pine for the old days - I really do. Things are insanely complex now and I don't like it. Unfortunately there are good reasons for the complexity.
Meh.
Containers provide solutions to the problems that someone else had. If you don't have those problems, then containers just create complexity and problems for you.
What problems do they solve? They solve, "My codebase is too big to be loaded on one machine." They solve, "I need my code to run in parallel across lots of machines." They solve, "I need to satisfy some set of regulations."
If you do not have any of those kinds of problems, DON'T USE CONTAINERS. They will complicate your life, and bring no benefit that you care about.