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:
- 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
My instance has 2 users. The domain name is endlesstalk.org
I host it on a k3s cluster with 2 nodes.
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!