2026-04-26 18:17 UTC
Oh wow, that’s really cool! I do use Caddy too.
Is it that your service/website is on both (low powered server and high powered one) or is it only on the high powered? So, it’s like
- the lower powered server knows it needs help (sounds a bit surreal to me, but perhaps it’s doable)
- or the lower powered server does not serve anything, but wakes up the high powered when the thing is accessed?
I guess that’s the 2nd thing, but it’s very cool indeed! That way you can really have very convenient things for free, as it’s super cheap to run any hardware for a very while on demand. I don’t mind waiting a minute or even two when I need to access something very infrequently and don’t want to run my server 24/7. I do exactly that, but I wake up it via LAN manually.
Replies (1)
-
@greybeard@feddit.online 2026-04-26 18:42
The low powered server is the Caddy server, all it does us act as a reverse proxy for everything in my house, giving it an SSL cert and doing things like WOL. The caddy config basically just says "Here's your reverse proxy target, if you don't get a response within one second, send a WOL packet, wait a couple of seconds, then try again". The only requirement is for you to do a custom build of caddy (this is done with a dockerfile), and to have WOL enabled on the high power server. It means the first web request for services on the high power server might take a few seconds, but everything after that is smooth.