Split Emby Front-End and Back-End

[UncleLeoTheDad 3]

This question is admittedly a bit of an odd one, but I figured I'd give it a try.

I currently have Emby running of a Windows PC.  It works well for streaming 4K, etc.  That said, it just sits there most of the day, sucking up electricity and only gets used here and there.  It made me think if there was some way to "split Emby" so that a smaller, more ecological machine like a rasberry PI stayed on all day to serve up the front end, the collection metadata, eta, while the "server" stayed mostly asleep and was only woken up by the front end when something was asked to be streamed.

Basically I'm trying to reduce the electrical cost of running the thing.  Not a terribly high priority, but something that just seemed wasteful.  One could argue "just shut it off until you need it", but I do have other people using it and don't want them to have to text me to start the machine every time they do.

Thoughts?

[Luke 42080]

HI, this is kind of the separation we have with app/server. Maybe your best bet is a smaller server machine with nas for holding your media.

Then once @AdrianW's long standing feature request of pre-caching images is finally done, then the nas will be able to stay sleeping until media is played.