test: wait for Guacamole readiness
This commit is contained in:
@@ -54,11 +54,13 @@ is `127.0.0.1:5002`; use a local SSH forward or a browser on the controller.
|
||||
Choose alternate ports with `--http-port` and `--tunnel-port` if either is in
|
||||
use. The VM must already be running. `up` checks the documented VM/snapshot
|
||||
identity but intentionally does not restore, start, stop, or reset the VM. It
|
||||
starts a small host-side watchdog for the SSH master. The watchdog reconnects
|
||||
after a transient Helium/SSH failure while preserving the same Docker-gateway
|
||||
listener, so an already-open Guacamole session can recover without restarting
|
||||
the containers. Its PID, stop marker, and diagnostic log are kept under the
|
||||
ignored `.runtime/` directory.
|
||||
starts a small host-side watchdog for the SSH master. Before printing the URL,
|
||||
`up` waits until the HTTPS gateway can serve `/guacamole/`; this prevents a
|
||||
browser login from racing Tomcat's Guacamole WAR deployment. The watchdog
|
||||
reconnects after a transient Helium/SSH failure while preserving the same
|
||||
Docker-gateway listener, so an already-open Guacamole session can recover
|
||||
without restarting the containers. Its PID, stop marker, and diagnostic log
|
||||
are kept under the ignored `.runtime/` directory.
|
||||
|
||||
All fixture-specific values have embedded, working defaults: the
|
||||
`helium-remote` SSH alias, Helium's loopback VRDE endpoint (`127.0.0.1:3389`),
|
||||
|
||||
Reference in New Issue
Block a user