Why is this? I’ve never used docker before and when I set up my server a couple years ago, I installed Debian, Apache, and MariaDB and got everything set up relatively easily.
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.
Because with docker you don’t even have to install and setup Apache and MariaDB. You run one command and it knocks out that whole process. Not go mention the security implications of completely seperating your software.
I can also speak from experience when I say it makes development and delivery of software soooo much easier. As a self hosted software developer I can promise you that if I created an instruction set to deploy the software I build bare metal rather than just containerizing it. No offense to fellow self hosters by any means, but if I require a multi step instruction set rather than a one liner docker command I will get more issues. Humans make mistakes, and when I can automate it out with container orchestration it absolutely makes it easier for the user.
I appreciate the response! When I set out to self-host, I made the decision to install everything separately, because I heard about docker and it sounded like, “plug in code and run”. And that’s something I didn’t want, only because it was a hobby and I wanted to learn more from a hands on experience. I learned a ton, sorting through those errors! If I did it over again, I’d probably use docker, based on your explanation, but I feel like that is an endeavor, in and of itself.
Docker? Without it life would be difficult so self host
Why is this? I’ve never used docker before and when I set up my server a couple years ago, I installed Debian, Apache, and MariaDB and got everything set up relatively easily.
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.
I actually just had to deal with this! So, I ended up spending time troubleshooting and rewriting some .conf files for Apache.
Because with docker you don’t even have to install and setup Apache and MariaDB. You run one command and it knocks out that whole process. Not go mention the security implications of completely seperating your software.
I can also speak from experience when I say it makes development and delivery of software soooo much easier. As a self hosted software developer I can promise you that if I created an instruction set to deploy the software I build bare metal rather than just containerizing it. No offense to fellow self hosters by any means, but if I require a multi step instruction set rather than a one liner docker command I will get more issues. Humans make mistakes, and when I can automate it out with container orchestration it absolutely makes it easier for the user.
I appreciate the response! When I set out to self-host, I made the decision to install everything separately, because I heard about docker and it sounded like, “plug in code and run”. And that’s something I didn’t want, only because it was a hobby and I wanted to learn more from a hands on experience. I learned a ton, sorting through those errors! If I did it over again, I’d probably use docker, based on your explanation, but I feel like that is an endeavor, in and of itself.