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.
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
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.
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.
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.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
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
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.
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.
Solid setup! Thanks for sharing.
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.