I was using webmin, but since my last server died and I’m making a new one, I decided I’d look into something different, personally I liked webmin but didn’t use most of its functionality and felt a little clunky for my basic use. I’ve also testran casaos but felt weirdly limited and couldn’t smoothly migrate docker containers to interact with its interface.

I can do with just the terminal, but it’s nice having a gui that I can glance at my phone and quickly do stuff like update and reboot.

I personally haven’t seen or found much conversation into the topic so I figured I’d ask and see what you peeps use and why.

  • ShortN0te@lemmy.mlEnglish
    13·
    5 days ago

    The cli.

    I have used management interfaces like coxkpit in the last but i do not really like it that much. I have E-Mail Notifications setup for updates via aptitude and monitor using prometheus and grafana and get additional notifications via prometheus alarm manager.

    For an easy to use docker interface i use dockge, since i found it in this use case to be faster with a good, working, independend Interface.

    But for the Linux underneath, for all 10-20 servers i managae, CLI.

  • Scrath@lemmy.dbzer0.comEnglish
    6·
    4 days ago

    Proxmox to manage my VMs, SSH for anything on the command line and portainer for managing my docker containers.

    One day I will switch probably switch to dockge so my docker-compose files are stored plain on the hard drive but for now portainer works flawlessly.

    • jimd@lemmy.caEnglish
      11·
      4 days ago

      dockge needs me to maintain my dockercompose on its own folder in /opt/ as root.

      I just wanna keep my compare in its own repos

      • Scrath@lemmy.dbzer0.comEnglish
        1·
        4 days ago

        Yeah, that would be the ideal scenario I guess.

        It should technically be possible by mapping the compose files into the opt folder via docker mounts but I think that’s an unreasonable way to go about this since every compose file would need a mounting point

  • poVoq@slrpnk.netEnglish
    13·
    5 days ago

    Cockpit is nice for that. The Podman integration of it is also useful.

  • BruisedMoose@piefed.socialEnglish
    4·
    4 days ago

    I had started out with CasaOS and ran it for a year or so. Last week, I took some time to move everything out of Casa’s file structure and cleaned up the compose files.

    For container management, I’m using Dockhand. It’s been great.

    Otherwise, like most others have said, SSH when I need to do more.

  • tofu@lemmy.nocturnal.gardenEnglish
    7·
    5 days ago
    • Proxmox GUI for restarting hosts or vms
    • Komodo for restarting containers
    • Forgejo for configuring and updating containers (deployed by komodo)
    • Ansible for OS updates
    • Prometheus + Grafana for monitoring

    Those for basic stuff, ssh for everything else.

  • atzanteol@sh.itjust.worksEnglish
    3·
    4 days ago

    Terraform, ansible and kubernetes (microk8s).

    K8s in particular has been a huge change to simplifying my network despite the complexities involved and the initial learning curve. Deploying and updating services is much easier now.

    • melfie@lemmy.zipEnglish
      1·
      4 days ago

      I run k3s and use Argo CD at work, but it always seemed overkill for my home server. I also would want to use self-hosted Forgejo instead of an external service, but I don’t care to spend time on a setup that bootstraps Forgejo, PostgreSQL and Argo CD, then has all of the above managed by Argo CD.

      • synae[he/him]@lemmy.dbzer0.comEnglish
        2·
        4 days ago

        Forgejo, I can’t help ya with that one

        Even though me and another guy set up Argo at work, I wasn’t gonna do it all over again - I pretty much just copied our manifests from work, swapped out the secrets and github urls, and was on the path to success. And the benefits cannot be understated

    • Fierro@piefed.socialOPEnglish
      1·
      5 days ago

      Whatever you interpret that as since my main goal here is to seed conversation, but the thing that I was thinking of when asking was a web gui with some live stats, doing some simple maintenance stuff, maybe manage or glance at docker/podman status and other services, etc.

      Since I’ve seen some conversations about documenting setups so they can be picked up and troubleshot by someone else unfamiliar with the setup like a family member, I expected it would be common to lower the friction for basic maintenance but seeing the amount of ssh comments makes me think otherwise, maybe more people use their servers exclusively for personal entertainment than I expected.

      • MalReynolds@slrpnk.netEnglish
        4·
        5 days ago

        more people use their servers exclusively for personal entertainment than I expected.

        Uh-huh, think of it like jigsaw puzzles…

        That said, I prioritize ease of maintenance and simplicity, still wouldn’t expect my family to pick it up in any reasonable amount of time, nor have the motivation, more’s the pity.

        I’ve moved to podman (quadlet) containers mostly, easy to read and edit, secure (mostly userspace), systemctl integration, autoupdate. I’ve done my distrohopping, fedora (in my case bazzite immutable) isn’t going anywhere, does everything I need. I run fairly lean, but have a bunch of stuff that can be spun up at a whim that I don’t use daily. It’s entertaining without being a burden, and useful stuff just happens.

        Honestly, ssh and btop cover most of my monitoring needs, serious stuff gets a notify-send to my laptop. I’ve tried the web gui stuff and I don’t look at it enough to justify it, I’m not a sysad monitoring hundreds of computers, it’s just a hobby.