Comment on 2025 Self-Host User Survey: Open for Submissions

• Tolookah@discuss.tchncs.de ⁨3⁩ ⁨weeks⁩ ago

  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.

  source

  • corsicanguppy@lemmy.ca ⁨3⁩ ⁨weeks⁩ ago

    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.

    source

    • Appoxo@lemmy.dbzer0.com ⁨3⁩ ⁨weeks⁩ ago

      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.

      source

      • corsicanguppy@lemmy.ca ⁨2⁩ ⁨weeks⁩ ago

        No need to look up how to do a clean install.

        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.

        source
  • waddle_dee@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

    I actually just had to deal with this! So, I ended up spending time troubleshooting and rewriting some .conf files for Apache.

    source
• madeofpendletonwool@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

  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.

  source

  • waddle_dee@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

    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.

    source