The problem is when one app requires a different apache(or some other random requisite) version than the other one, docker just deals with that so I don’t have to. That’s what I like about it.
Dependency hell is self-inflicted, but sparkle-junkie devs are complicit: it’s their fault they don’t know of long-term-support enterprise OSes and don’t use one as a primary port.
The suggestion you don’t know that enterprise OSes have been doing clean installs and removals of a product and all its dependencies for 25 years as a critical test before issuing said packages suggests you’re working around too many problems without solving them.
We did devops by pxe-based kickstart and then simple package updates before devops was even a word. It still does better than Ansible does now.
The problem is when one app requires a different apache(or some other random requisite) version than the other one, docker just deals with that so I don’t have to. That’s what I like about it.
Dependency hell is self-inflicted, but sparkle-junkie devs are complicit: it’s their fault they don’t know of long-term-support enterprise OSes and don’t use one as a primary port.
But it also keeps the junk in a near little area which I can easily get rid of.
No need to look up how to do a clean install.
I would say it’s purpose can be used like a live-ISO of an OS.
The suggestion you don’t know that enterprise OSes have been doing clean installs and removals of a product and all its dependencies for 25 years as a critical test before issuing said packages suggests you’re working around too many problems without solving them.
We did devops by pxe-based kickstart and then simple package updates before devops was even a word. It still does better than Ansible does now.
I actually just had to deal with this! So, I ended up spending time troubleshooting and rewriting some .conf files for Apache.