With the recent Proxmox 9 release, many of us have the upgrade ahead or already done. What about you, and how do you generally approach updating your services? Which other updates are you looking forward to or is it just an annoying chore?

Also the usual - let us know what you are currently working on, what problems you are encountering and what you are excited about.

As for updates, I update my machines semi-regularly with Ansible. The Proxmox 9 update was unspectacular (good thing!), I just had to change some things in my Promox-post-install automation (nag bar removal and package sources). I still plan to get a merge request based update process for my containers as mentioned here but I’m just not there yet. That guide was also posted on reddit recently and got some traction.

I also spent some time yesterday to organize my nginx logs, they basically all got their own folder in /var/log/nginx with their own access log file by adding access_log /var/log/nginx/$server_name/access.log vhost_combined; to each config. Error log file paths can’t contain variables so I kept them in the default file so far.

Recently enabled wireguard (easy setting in my FritzBox router) and stopped exposing some of my services to the internet. That process isn’t finished yet though as I’ll need to switch to wildcard certificates in order to keep valid SSL for the now local-only services.

  • Samsy@lemmy.mlEnglish
    6·
    2 hours ago

    I have never understood the hype surrounding proxmox. What makes proxmox so irreplaceable?

    • tofu@lemmy.nocturnal.gardenOPEnglish
      6·
      2 hours ago

      Super reliable virtualization and management features. Snapshots, auto backups, live migrations across physical hosts, high availability are what I like the most.

    • sj_zero@lotide.fbxl.net
      4·
      2 hours ago

      I moved to proxmox earlier this year and it quickly became a huge deal for me.

      One nice thing is that I can easily create lxc containers for each service that has exactly what that service needs. Each service lives in a container that acts a lot like bare metal.

      A second nice thing is it’s really easy to administer everything remotely. All your machines end up accessible through the proxmox interface, and you can hop into virtual machines or lxc containers via the web.

      A third thing is you can easily handle hot standby and backups through an easy UI.

      Totally changed the game for me.

    • AreaKode@lemmy.worldEnglish
      2·
      2 hours ago

      If you know Linux or are willing to learn, it is very easy to use. If not, it’s going to be a bit of a chore. Some things are just easier to do via CLI.

    • McMonster@programming.devEnglish
      2·
      2 hours ago

      I’ve tried it a few times, never stuck. I guess it’s just convenience, it is a well integrated piece of software, especially if you use both LXC and VMs. Personally I keep using virt-manager and Cockpit.

  • themachine@lemmy.worldEnglish
    2·
    1 hour ago

    DC my server is at is shutting down so I have to bring everything home. Conveniently I just got hooked up with symetric 1G fiber so that’s not too much of a problem now thankfully.

    Currently exploring docker swarm as a method of using one of my external VPSs to route all external traffic though it to my hardware at home on my tailnet.

    Swarm isn’t required for this but figured I’d play around with it.

  • stoy@lemmy.zipEnglish
    3·
    2 hours ago

    I am currently in the final phase of building my first own built NAS.

    (I have an oooooold Intel NAS, that I don’t really use anymore…)

    I need to populate the case with storage drives, I need to add an Intel GPU, a 10gbit NIC, and possibly add an HBA to add two SSDs for VM storage.

    Currently I have a:

    • Jonsbo N4 case
    • Asrock B550m Pro4
    • AMD Ryzen 4600G
    • 32GB RAM
    • Kingston boot SSD
    • Corsair SF750 PSU

    I am running TrueNAS on it, that was just installed to make sure that it is working, but I am planning on running it going forward, as I am mostly looking to run the server as a filserver.

  • [object Object]@sh.itjust.worksEnglish
    4·
    3 hours ago

    sops-nix + rootless podman turns out to be much tricker than I imagined. Spent like 2 days over this shit just to get it in the central config when I could have just manually loaded the config files and change the permission… I eventually solved it by running rootlesskit in the activation script to copy the decrypted file into a temporary folder and changing the permission to the correct sub-user. Not worth the time though.