Don't proxy if not modified

[dispherical]

No description provided.

[hello-smile6]

Assuming that everyone uses caddy would be bad imo, also, if they've created a domain, they clearly aren't inactive. Why not store a value in the database once a user shows signs of existing (e.g. having more than just their user domain configured or reconfiguring their user domain)? It doesn't seem like any actual memory savings would occur from this, since we'd still be running hundreds of caddy processes.

[dispherical]

Assuming that everyone uses caddy would be bad imo, also, if they've created a domain, they clearly aren't inactive. Why not store a value in the database once a user shows signs of existing (e.g. having more than just their user domain configured or reconfiguring their user domain)? It doesn't seem like any actual memory savings would occur from this, since we'd still be running hundreds of caddy processes.

This was your suggestion...

Can we make something that runs whenever a user's Caddyfile is first modified by a user and make the global caddy not actually proxy to the user's caddy until the first modification happens to decrease memory usage and avoid wasting RAM on users who haven't done anything yet?