The theory is that you could have the hot reloading test server on standby to run tests, updating files based on the git diff.
This is support currently disabled, you can only use the daemon in a capacity of client / server on localhost.
There's a few concerns before this is doable:
Security - the RPC server would need to be replaced with one that uses an encrypted connection
Consistency - the hot reloading daemon needs to work good enough on a consistent basis to make this actually save time, with the times it fails to correctly update being rare and far between. I would not consider this until this project moves out of alpha into beta.
Control - there needs to be a prescribed way of running this that allows you to restart the server easily if it does happen to get in a bad state. Ideally, it self-detects or tries again if it possibly got into a bad state.
Pooling - this would likely need pooling where servers can get cycled out, increasing the capacity while also allowing for things like cycling the servers on test errors or unexpected behavior.
The theory is that you could have the hot reloading test server on standby to run tests, updating files based on the git diff.
This is support currently disabled, you can only use the daemon in a capacity of client / server on localhost.
There's a few concerns before this is doable: