Selfhosted
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.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
I'm aware of databases that support HA, but the vast majority of self-hosted apps I've encountered use file storage, even if they have a database as well. It sounds like you're proposing shared storage like an NFS share. But if you're upgrading nodes, at some point you have to upgrade the node hosting the shared storage right? Wouldn't that take down all services? Unless you use a distributed storage system, but I've heard those can get very complicated...
Kubernetes makes distributed storage easy.
Basically, all the components get deployed for you, since that's part of what kubernetes is good at.
And then, services/containers can provision storage by requesting storage via making a "claim" and whatever distributed storage providee you have gives it to you.
Have you tried using Ceph or other distributed storage systems in your kubernetes cluster?
Well, I run a one node cluster...
But yes, I did use ceph via rook-ceph, because Openstack (a locally hosted AWS alternative), at least the Kubernetes version, wanted a ceph "cluster" to store stuff on.
Longhorn is much easier. Although again, my "cluster" was one node. I deployed it because I wanted snapshots.
Wow cool! I believe you're the first person I've met that actually used a cluster FS (in their homelab at least). I looked into it myself but it felt like nobody was really using it so I didn't bother.
Does it involve much more work or is it a fairly transparent replacement to traditional storage options? Assuming one is already using Kubernetes. I'm wondering if it's worth it to switch to a cluster FS for everything, like Radicale or Tiddlywiki.
On kubernetes it's pretty much the same amount of work. Every possible storage option exposes a generalized, abstracted "storageclass", from which storage can be provisioned and mounted into containers.
https://kubernetes.io/docs/concepts/storage/storage-classes/