root/fusion
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: correct a stale dev-tunnel comment describing the removed fallback

Browse Source 
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
gsxdsm
2026-08-18 20:40:41 -07:00
parent ce69558c7a
commit 8d76af3e5f
1 changed files with 3 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
scripts/dev-with-memory.mjs
View File

@@ -106,8 +106,9 @@ normal Fusion already holding 4040, the tunnel pointed at THAT instance and serv
under a dev-looking URL. Wait for the child's listening report and tunnel the port it actually got.
An explicit `--tunnel=PORT` names a target the operator chose (a Vite server the dev child knows
nothing about), so it is used immediately and never waits. If the report never arrives the tunnel
still comes up on the configured port, since a mis-targeted preview beats no preview at all.
nothing about), so it is used immediately and never waits. Without one the wrapper WAITS for the
report rather than falling back to the configured port: publishing a guess pointed a dev-looking URL
at whatever else held that port, which is the exact confusion this fix exists to remove.
*/
/*
FNXC:DevTunnel 2026-08-19-03:38: