Self Hosting My Way - Nextcloud
oranki.net
Nextcloud, the go-to for most self-hosters, doesn’t really need introductions. This post has been long in the making, mainly due to my recent change from running everything with Podman to Kubernetes with k3s. Long story short, k8s is fun and interesting, but Podman pods are rock solid. I had an accident on new year configuring cluster ingress, and had to make a quick decision on whether to spend the night figuring it out, or switch back to trusty old ways. I chose the latter.

My take on simple self-hosted Nextcloud community image, with PostgreSQL and Redis. Managed as a single pod using Podman + Quadlet.

  • PullPantsUnsworn@lemmy.mlEnglish
    1·
    2 hours ago

    This is on my todo list. I use Docker-compose for it’s simplicity, but Docker is a security nightmare. If you are not careful, it would expose your Nextcloud instance to the whole world. Podman integrates nicely with firewalld which gives me zone based rules. Can’t wait to do this. But I will give sometime to let Quadlet get stabilized and popular.

  • lucid@lemmy.dbzer0.comEnglish
    7·
    6 hours ago

    I always appreciate people putting up quadlet content. I’ve switched over almost my entire lab to it aside from Nextcloud (so thanks!) and a couple containers that have weird network quirks

    • mosiacmango@lemm.eeEnglish
      2·
      4 hours ago

      Amen to the weird network quirks. I was trying to use the Tailscale docker sidecar examples, but could not work put how to use them in quadlets.

      I expect i need to make a .pod or .network file and comingle the quadlets that way, but just setting up a dedicated tailscale subnet router VM with /32 allowed addresses was about 10x easier.

      • lucid@lemmy.dbzer0.comEnglish
        2·
        3 hours ago

        My most recent one I got working was Gluetun. And yeah in order to use it I have my entire arr stack in the same gluetun pod. The http proxy also works but I only wanted that as a last resort.