Selfhosted

40183 readers

576 users here now

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!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

GitHub - anthr76/lemmy-ks: Kustomizations and published OCI manifests to deploy Lemmy on Kubernetes (github.com)

submitted 1 year ago by anthr76@lemmy.kutara.io to c/selfhosted@lemmy.world

6 comments fedilink hide all child comments

In a previous post I was looking gauge folks interest on who runs Lemmy on Kubernets. Given the positive feedback I decided to make the manifests I'm using to deploy it available to anyone.

The README and issues touches more in depth but hopefully in a few days or weeks this can a simple and fast way (similar to Lemmy's provided compose) to deploy Lemmy :)

top 4 comments

sorted by: hot top controversial new old

[–] sudneo@lemmy.world 4 points 1 year ago

Very interesting! I will try to give it a go on my cluster, I was just asking myself if someone was doing this!

[–] fox@lemmy.fakecake.org 3 points 1 year ago (1 children)

i suggest pointing pictrs to (an external) S3 backend instead of using a pvc in your README example. minio is much easier to deploy than ceph.

[–] anthr76@lemmy.kutara.io 3 points 1 year ago* (last edited 1 year ago) (1 children)

I am :) you still need a PVC for the db though. Granted I plan on now moving that to nvme block storage.

[–] fox@lemmy.fakecake.org 2 points 1 year ago

you're right, i completely forgot that it has this strange local DB. that's disappointing.

personally i would just run it outside of k8s then because it's not stateless and pvc is a PITA.

load more comments