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
Have you been able to load balance with multiple containers? Im not really familiar with k8s
load balancing is automatic between pods thanks to Services: https://kubernetes.io/docs/concepts/services-networking/
I also use kubernetes to run my Lemmy instance. Sadly,
pictrsuses their own "database" file which can only be opened by a single pod because it refuse to run if the "database" lock is already acquired by another pod, making scaling up the number of pods impossible. I wish they use postgres instead of inventing their own database. I suspect this is one of the reasons why those large Lemmy instances have difficulty scaling up their server.You mean pictrs can't scale, or the other pods cannot as well? I separated lemmy-ui, the backend, and pictrs into different pods. Haven't tried scaling anything yet though, but I did notice the database issue with pictrs when RollingRestart, had to switch to Recreate.
Only pictrs that can't scale. Lemmy ui and backend seems to be stateless.
I saw that Lemmy container has scheduled jobs. How did you handled that? IDK I’m not sure about is Lemmy really “stateless”.
https://lemmy.world/post/920294
Right, that's a good point.
So far it's working quite well, however for a micro-sized instance it's no surprise. Worst case scenario I can do the same thing as the admins of lemmy.world did: create a dedicated scheduling pod using the same docker image as the normal ones, but exclude it from the Service's target, so it won't receive any incoming traffic.
The rest of the pods can then be dedicated to serve traffic with their scheduling functionality disabled.