feat: isolate simultaneous RDP fixture profiles
This commit is contained in:
+3
-1
@@ -210,7 +210,9 @@ self-signed HTTPS Guacamole lifecycle; it must be started only after the native
|
||||
fixture controller has prepared and leased the VM, and stopped before reset.
|
||||
For a public hostname with an AAAA record, its `up --bind 0.0.0.0` mode also
|
||||
tracks an IPv6-to-IPv4 forward; verify `ipv6_forward=active` before debugging
|
||||
a browser stuck at “Waiting for response”.
|
||||
a browser stuck at “Waiting for response”. If several already-running VMs need
|
||||
browser access at once, use the documented `RDP_ACCESS_PROFILE` and matching
|
||||
host/VRDE/HTTP/tunnel-port overrides in the helper README.
|
||||
|
||||
The Linux production Compose asset has a separate, loopback-only smoke lane. It
|
||||
uses a disposable self-signed key only under the ignored `.test-runs` tree,
|
||||
|
||||
Reference in New Issue
Block a user