dioxus-cli version 0.6.3 randomizes server file name, making it impossible to configure firewall

[johnny-smitherson]

Problem

In some environments, the firewall must always be on. This means each executable that wants to connect to the network in any way, must be manually allowed by the user by clicking a button. On some platforms, like "Windows Advanced Firewall", users cannot make any wildcard/regex rules, only exact path rules - so executable names must be predictable.

dioxus-cli version 0.6.3 now randomizes the server binary name by attaching some random text at the end of the file, just before executing it.

Here it is in task manager:

This means:

• firewall configurations do not work anymore, as the filename will change every rebuild.
• using "Windows Advanced Firewall", the user is bombarded with fullscreen modals like these:

Steps To Reproduce

Steps to reproduce the behavior:

• dx --version --> dioxus 0.6.3 (fc1f1c2)
• dx new, full stack = yes, platform = web
• dx serve --platform web generates different executable name every rebuild

Expected behavior

Execute from the same path every time.

Or, if really necessary, alternate between server.exe and server.exe-1 so the user only clicks "allow" twice. Through the "access denied because program open" windows-specific problem might be better solved by closing the old process before overwriting?

Screenshots

See above

Environment:

• Dioxus version: 0.6.3 + 0.6.2
• Rust version: 1.87 nightly
• OS info: Windows 11
• App platform: fullstack web

Questionnaire

Workaround

cargo binstall [email protected] --force -y

[ealmloff]

We only need unique names for the assets that get served. I believe the server name changes on windows so we can keep the old server running until the new bundle is fully built, but we can alternate between just two names instead of generating a unique name every time. This method would need to be modified