It appears that from the time that the app is launched and is passing all readiness checks, to the time it is accessible through the public URL, there is a delay of ~3 minutes.
Since the app is already running, I am assuming the delay is the time takes to propagate DNS records.
curl: (6) Could not resolve host: foo-1bcc73b2.fly.dev
Is there a quick way to connect to the application? Doesn’t even need to be public Internet.
edit: Surprising DNS propagation is still slow enough to matter (despite recent improvements). Per this thread, may be
bluegreen deployment strategy with 3+ VMs might help: how do fly.io deploys work? - #9 by jsierles
You could connect to the VM over
6pn which (apparently) may have faster propagation (see), but may also be down at times (ex), and come with gotchas (like).
- using Wireguard / connecting to a port on an app
- Specify instance-id in fly-replay header - #10 by ignoramous
- How to copy files off a VM - #8 by CabelloMania