Interesting writeup. I’m curious about the resource usage of the Lemmy backend and frontend deployments. Do you have any insights on the resource utilization of these deployments?
Interesting writeup. I’m curious about the resource usage of the Lemmy backend and frontend deployments. Do you have any insights on the resource utilization of these deployments?
Hosting at Hetzner.
Server configuration may appear a bit weird. I have the storage managed with longhorn. It’s not on the nodes, but mounted to them.
Definitely LTB_iel. I really hope the new iteration can find its former glory again.
While setting up pict-rs on my cluster I noticed a pict-rs environment variable to convert all uploaded pictures to the png format. That may also be activated. I guess that makes de-duplication way easier.
I am running Lemmy in a Kubernetes cluster. You can find the helm charts and a short documentation here: https://github.com/grouvie/lemmy_help
I am happy to help should anyone have further questions. :)
What does your setup look like? Using traefik instead of nginx shouldn’t be a big problem.
I created a helm chart to help setting up Lemmy on kubernetes. I am already using it successfully for my instance. You can find the charts and a short documentation here:
https://github.com/grouvie/lemmy_help
I’m happy to help with further questions and problems, too.
I deployed Lemmy on my kubernetes cluster. You can find a short guide and my helm charts here:
https://lemmy.help/post/6845
https://github.com/grouvie/lemmy_help
I am using argoCD to manage my charts. Feel free to contact me if you have any questions.