this post was submitted on 17 Jun 2023
42 points (100.0% liked)

Selfhosted

40134 readers
545 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

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 :)

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 2 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.

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago)

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