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.
Resources:
- 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
My instance has 2 users. The domain name is endlesstalk.org
I host it on a k3s cluster with 2 nodes.
Is there a way to host with high availability? Or is that a kubernetes feature?
K8s is just a huge abstraction over your clusters, the real question is if the software/containers support HA.
I’ve been meaning to test it for a while now, but have just been running VMs/Docker. Will check it out.
You can definitely have high availibillity without kubernetes, but its easier(For me atleast) with kubernetes.
What HA options exist outside of k8s?
For container orchestration, which is mostly what k8s provides, then you could use docker swarm or nomad. You could use docker-compose with multiple replicas of the wanted container + a load balancer to divide the load.
In general I don't think k8s/k3s is needed for hosting lemmy yet, but since I have a setup for k3s, it is easier for me to use it.
Nice, thanks for the info.
how do you handle the sled state for pictrs with 2 nodes? I've been having some trouble with it.
I have only 1 container of pictrs running(with no scaling) and are using longhorn for storage, so if the pictrs container switches node, then longhorn handles it for me.
I see, thanks. What volume(s) are you persisting that way exactly? I mean the internal path that pictrs is using.
The internal path, I'm persisting is
/mnt, but I also use an older version of pictrs(0.3.1). Think the newer version uses a different path.I also needed to add the following for the pictrs container to work correctly.
Thanks a lot!