this post was submitted on 01 Mar 2025
30 points (96.9% liked)

Selfhosted

43808 readers
429 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 2 years ago
MODERATORS
 

I've got a mini pc which is running always and another one which consumes a lot more power for e.g. jellyfin.

Can I configure it such that the jellyfin server only boots if I connect to it? E.g. I try to connect to jellyfin.y.com and then the server boots because the mini pc tries to connect to it.

I already figured out how to let it sleep automatically as soon as nobody is watching.

Edit: can I add the magic package to the reverse proxy?

you are viewing a single comment's thread
view the rest of the comments
[–] Mubelotix@jlai.lu 2 points 1 week ago (1 children)

I made a tool that can hibernate systemd services when no request get through their associated nginx service. Using it on jellyfin, works great

[–] sugar_in_your_tea@sh.itjust.works 2 points 1 week ago (1 children)

I assume this works like the reverse of socket activation? If so, that's pretty rad!

That said, that doesn't really solve OP's problem, and I'm not exactly sure what it's solving for you. Jellyfin doesn't really use any resources when idle, so it's not going to save on power or anything like that.

That said, you could probably create an interesting service like this. Basically, if the last interesting service shuts down, you shut the whole machine down, and then use WoL to start it back up when someone wants it. Tune it a bit to reduce how often it reboots (i.e. extend life of your disks) and reduce boot times (i.e. don't mount the RAID until it's needed), and it could be really cool!

[–] Mubelotix@jlai.lu 2 points 1 week ago (1 children)

Exactly. It's like socket activation but plugged into nginx. It might or might not fit OP's use case, as when you have many small services like jellyfin, ram usage starts adding up. Adding automatic shutdown is a great idea

I can see that, especially if running on limited hardware. My server has way more RAM than it needs though (16GB), so saving 50MB here and there isn't very important.