• MXX53@programming.dev
    link
    fedilink
    English
    arrow-up
    2
    ·
    2 days ago

    This is interesting to me. I run all of my services, custom and otherwise, in docker. For my day job, I am the sole maintainer of all of our docker environment and I build and deploy internal applications to custom docker containers and maintain all of the network routing and server architecture. After years of hosting on bare metal, I don’t know if I could go back to the occasional dependency hell that is hosting a ton of apps at the same time. It is just too nice not having to think about what version of X software I am on and to make sure there isn’t incompatibility. Just managing a CI/CD workflow on bare metal makes me shudder.

    Not to say that either way is wrong, if it works it works imo. But, it is just a viewpoint that counters my own biases.

    • smiletolerantly@awful.systems
      link
      fedilink
      English
      arrow-up
      1
      ·
      5 hours ago

      Sorry, I should have mentioned: liking bare-metal does not mean disliking abstraction.

      I would absolutely go insane if I had to go back to installing and managing each and every services in their preferred way/config file/config language, and to diy backup solutions, and so on.

      I’m currently managing all of that through a single nix config, which doesn’t only take care of 90% of the overhead, it also contains all config in a single, self-documenting, language.