I’ve seen a lot of different enterprise and personal use distros for servers, but what do you guys use?

I’m planning on using Debian but was wondering if there are any other good free options to consider.

    • qprimed@lemmy.mlEnglish
      18·
      6 months ago

      creative is great, but sometimes you really just want your fleet of servers to do their fleet of servers thing. no fuss, no hassle. 100% solid and stable. learn the “debian way” and life is grand.

      debian saved my marraige and raised my kids - ok, not really, but almost.

  • RegalPotoo@lemmy.worldEnglish
    25·
    6 months ago

    Debian. When I have time to mess about with server stuff, I want to be doing the thing I want to do rather than fixing whatever broke in the most recent set of updates

    • haui@lemmy.giftedmc.com
      13·
      6 months ago

      I switched from ubuntu to debian on 2 machines recently and the difference is drastic. No bloat (snap), no asking for pro membership, just works.

  • Kuadhual@lemm.ee
    16·
    6 months ago

    What we use in my office, depends on the type of servers:

    • For virtual server (we made a golden template of it) we use Debian 12
    • For virtualization host/ganeti cluster we use Debian 11
    • For NAS, we use OpenMediaVault (based on Debian)
      • Kuadhual@lemm.ee
        3·
        6 months ago

        I would like to default to debian 12 if I have to start fresh.

        The Ganeti Cluster was installed on Debian 10 then when 11 launched, I upgraded it. It’s a 10 nodes cluster and I just don’t have time to upgrade it yet. The last update to 11 took me a week to troubleshoot.

    • Midnight Wolf@lemmy.worldEnglish
      6·
      6 months ago

      I did this, for flexibility and to tinker without screwing myself.

      But then my first install was Debian to run my docker containers sooooo

  • c10l@lemmy.world
    8·
    6 months ago

    Debian.

    Proxmox (which is heavily Debian) if the use case is to host VMs and/or LXC containers. Debian on those.

    • barsquid@lemmy.world
      1·
      6 months ago

      I’d go with basic Debian and Incus over Proxmox. I think Proxmox modifies the kernel but I’m not sure why that is necessary? I’ve had kinda buggy experiences with some installations and with their UI.

    • jimmy90@lemmy.world
      6·
      6 months ago

      NixOS is perfect for server OS. hope in future a little more orchestration tools make it even easier to manage clusters of NixOS instances

      • barsquid@lemmy.world
        4·
        6 months ago

        Have you seen NixOps? Curious if that’s getting close to what you want or not.

        I think I also saw another similar idea a while back but cannot recall the name, might just be a wrong memory.

  • boredsquirrel@slrpnk.net
    5·
    6 months ago

    I literally once rented a VPS, installed Debian 12, configured automatic updates, installed tor, set the max limit to the VPS limit, enabled the tor relay server.

    And now I am unable to login and that thing is just running lol. For the good of the Tor network?!

  • barsquid@lemmy.world
    5·
    6 months ago

    Debian is a great choice. I’m on Debian and it is solid.

    I do have one I like better: I’m transitioning to Fedora IoT from Debian for my homelab stuff. I like using their atomic desktop distros, I want to understand them better, and it seems like a great combination of recent kernel and system stability.

    • FizzyOrange@programming.dev
      2·
      6 months ago

      Interesting I hadn’t heard of these “atomic” distros. There isn’t really much description of what exactly is atomic about them though - all you get is “The whole system is updated in one go”. Can you explain it?

      • michael_palmer@lemmy.sdf.org
        3·
        6 months ago

        It works similarly to Android and iOS. The system partition is read-only, and each new system update is applied as a new system partition image. All user apps are kept separate from the system and are sandboxed.

      • barsquid@lemmy.world
        2·
        6 months ago

        I believe the “atomic” action is updating the kernel and all the base packages together such that either the whole thing succeeds or the existing system is unchanged. If the system update is atomic, you cannot be stuck in a partially updated state with new versions of some packages and previous versions of others. Naturally something like that lends itself to making rollbacks easier if it does break, much easier than trying to undo an update on a more traditional distro where they do the update in place.