this post was submitted on 02 Jul 2023
23 points (96.0% liked)

Selfhosted

39250 readers
260 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
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 3 points 1 year ago (1 children)

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

[–] [email protected] 6 points 1 year ago (1 children)

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.

[–] [email protected] 1 points 1 year ago

Do they have a write up on their setup?