Tests for basic server deployment in deploy-mode
Fixed example servers to use reconnect-on-error strategy
Fixed example servers to use reconnect-on-error strategy
In deploy mode, only watch the PID that was spawned at the beginning of the process. Fairly logical, huh?
Definitely don't print the PID list every processor tick. That's bad.
More robustly handle repeated restarts
Generally added more robustness against various problems with premature disconnects and also issues when many serverswap-deploy instances are started at once.
Added a condition to the spawn-many-at-once test: localhost:8080 must always be accessible. Fails fairly consistently after 16 deployers at once try to grab the resource.
Slightly more robust when many deploy processes are started at once.
1.4.4: basic unit tests, some stress-tests and general robustness against deploy processes and servers stacking up.