On macOS, after running magebox global stop, the web ports (e.g. 80, 443) remain occupied. This is because the LaunchDaemon responsible for binding those ports is not unloaded as part of the stop flow. This means that after stopping MageBox, other local dev tools or services attempting to bind to port 80/443 will fail with an address already in use error.
Suggested addition
The magebox global command set should expose this explicitly, e.g.:
magebox global stop # stops services AND unloads the LaunchDaemon
magebox global start # loads the LaunchDaemon AND starts services
So that users have a clean, predictable way to fully hand back system ports when MageBox is not in use.
On macOS, after running
magebox global stop, the web ports (e.g. 80, 443) remain occupied. This is because the LaunchDaemon responsible for binding those ports is not unloaded as part of the stop flow. This means that after stopping MageBox, other local dev tools or services attempting to bind to port 80/443 will fail with an address already in use error.Suggested addition
The magebox global command set should expose this explicitly, e.g.:
So that users have a clean, predictable way to fully hand back system ports when MageBox is not in use.