Three script-level port UX issues found and fixed:
== install.sh: re-install with PANEL_PORT now updates existing config ==
write_config previously returned early when config.yaml already existed,
ignoring PANEL_PORT env var. Re-running 'PANEL_PORT=9000 bash install.sh'
on an existing install silently kept the old port.
Fix: when config.yaml exists and PANEL_PORT/THREE_M_UI_PORT is explicitly
set, sed-update the port/listen/public_url in the existing file. First-
time install (no config.yaml) still writes full config with random keys.
== update.sh: show panel port after successful update ==
Update completed with no indication of which port the panel is on.
Users had to check config.yaml manually.
Fix: after '[5/5] Update completed', read server.port from config.yaml
and display:
Panel: http://SERVER_IP:<port>/
(to change port: 3m-ui config port <new-port>)
Also added CONFIG_DIR constant (was missing).
== uninstall.sh: show previous panel port before removing config ==
Uninstall removed config without telling the user what port was in use.
Fix: before rm -rf $CONFIG_DIR, read and display:
Previous panel port: <port>
fix(scripts): install/update/uninstall port handling
Three script-level port UX issues found and fixed:
== install.sh: re-install with PANEL_PORT now updates existing config ==
write_config previously returned early when config.yaml already existed,
ignoring PANEL_PORT env var. Re-running 'PANEL_PORT=9000 bash install.sh'
on an existing install silently kept the old port.
Fix: when config.yaml exists and PANEL_PORT/THREE_M_UI_PORT is explicitly
set, sed-update the port/listen/public_url in the existing file. First-
time install (no config.yaml) still writes full config with random keys.
== update.sh: show panel port after successful update ==
Update completed with no indication of which port the panel is on.
Users had to check config.yaml manually.
Fix: after '[5/5] Update completed', read server.port from config.yaml
and display:
Panel: http://SERVER_IP:<port>/
(to change port: 3m-ui config port <new-port>)
Also added CONFIG_DIR constant (was missing).
== uninstall.sh: show previous panel port before removing config ==
Uninstall removed config without telling the user what port was in use.
Fix: before rm -rf $CONFIG_DIR, read and display:
Previous panel port: <port>
fix(scripts): install/update/uninstall port handling
Three script-level port UX issues found and fixed:
== install.sh: re-install with PANEL_PORT now updates existing config ==
write_config previously returned early when config.yaml already existed,
ignoring PANEL_PORT env var. Re-running 'PANEL_PORT=9000 bash install.sh'
on an existing install silently kept the old port.
Fix: when config.yaml exists and PANEL_PORT/THREE_M_UI_PORT is explicitly
set, sed-update the port/listen/public_url in the existing file. First-
time install (no config.yaml) still writes full config with random keys.
== update.sh: show panel port after successful update ==
Update completed with no indication of which port the panel is on.
Users had to check config.yaml manually.
Fix: after '[5/5] Update completed', read server.port from config.yaml
and display:
Panel: http://SERVER_IP:<port>/
(to change port: 3m-ui config port <new-port>)
Also added CONFIG_DIR constant (was missing).
== uninstall.sh: show previous panel port before removing config ==
Uninstall removed config without telling the user what port was in use.
Fix: before rm -rf $CONFIG_DIR, read and display:
Previous panel port: <port>
fix(scripts): install/update/uninstall port handling
Three script-level port UX issues found and fixed:
== install.sh: re-install with PANEL_PORT now updates existing config ==
write_config previously returned early when config.yaml already existed,
ignoring PANEL_PORT env var. Re-running 'PANEL_PORT=9000 bash install.sh'
on an existing install silently kept the old port.
Fix: when config.yaml exists and PANEL_PORT/THREE_M_UI_PORT is explicitly
set, sed-update the port/listen/public_url in the existing file. First-
time install (no config.yaml) still writes full config with random keys.
== update.sh: show panel port after successful update ==
Update completed with no indication of which port the panel is on.
Users had to check config.yaml manually.
Fix: after '[5/5] Update completed', read server.port from config.yaml
and display:
Panel: http://SERVER_IP:<port>/
(to change port: 3m-ui config port <new-port>)
Also added CONFIG_DIR constant (was missing).
== uninstall.sh: show previous panel port before removing config ==
Uninstall removed config without telling the user what port was in use.
Fix: before rm -rf $CONFIG_DIR, read and display:
Previous panel port: <port>
fix(scripts): install/update/uninstall port handling
Three script-level port UX issues found and fixed:
== install.sh: re-install with PANEL_PORT now updates existing config ==
write_config previously returned early when config.yaml already existed,
ignoring PANEL_PORT env var. Re-running 'PANEL_PORT=9000 bash install.sh'
on an existing install silently kept the old port.
Fix: when config.yaml exists and PANEL_PORT/THREE_M_UI_PORT is explicitly
set, sed-update the port/listen/public_url in the existing file. First-
time install (no config.yaml) still writes full config with random keys.
== update.sh: show panel port after successful update ==
Update completed with no indication of which port the panel is on.
Users had to check config.yaml manually.
Fix: after '[5/5] Update completed', read server.port from config.yaml
and display:
Panel: http://SERVER_IP:<port>/
(to change port: 3m-ui config port <new-port>)
Also added CONFIG_DIR constant (was missing).
== uninstall.sh: show previous panel port before removing config ==
Uninstall removed config without telling the user what port was in use.
Fix: before rm -rf $CONFIG_DIR, read and display:
Previous panel port: <port>
fix(scripts): install/update/uninstall port handling
Three script-level port UX issues found and fixed:
== install.sh: re-install with PANEL_PORT now updates existing config ==
write_config previously returned early when config.yaml already existed,
ignoring PANEL_PORT env var. Re-running 'PANEL_PORT=9000 bash install.sh'
on an existing install silently kept the old port.
Fix: when config.yaml exists and PANEL_PORT/THREE_M_UI_PORT is explicitly
set, sed-update the port/listen/public_url in the existing file. First-
time install (no config.yaml) still writes full config with random keys.
== update.sh: show panel port after successful update ==
Update completed with no indication of which port the panel is on.
Users had to check config.yaml manually.
Fix: after '[5/5] Update completed', read server.port from config.yaml
and display:
Panel: http://SERVER_IP:<port>/
(to change port: 3m-ui config port <new-port>)
Also added CONFIG_DIR constant (was missing).
== uninstall.sh: show previous panel port before removing config ==
Uninstall removed config without telling the user what port was in use.
Fix: before rm -rf $CONFIG_DIR, read and display:
Previous panel port: <port>
fix(scripts): install/update/uninstall port handling
Three script-level port UX issues found and fixed:
== install.sh: re-install with PANEL_PORT now updates existing config ==
write_config previously returned early when config.yaml already existed,
ignoring PANEL_PORT env var. Re-running 'PANEL_PORT=9000 bash install.sh'
on an existing install silently kept the old port.
Fix: when config.yaml exists and PANEL_PORT/THREE_M_UI_PORT is explicitly
set, sed-update the port/listen/public_url in the existing file. First-
time install (no config.yaml) still writes full config with random keys.
== update.sh: show panel port after successful update ==
Update completed with no indication of which port the panel is on.
Users had to check config.yaml manually.
Fix: after '[5/5] Update completed', read server.port from config.yaml
and display:
Panel: http://SERVER_IP:<port>/
(to change port: 3m-ui config port <new-port>)
Also added CONFIG_DIR constant (was missing).
== uninstall.sh: show previous panel port before removing config ==
Uninstall removed config without telling the user what port was in use.
Fix: before rm -rf $CONFIG_DIR, read and display:
Previous panel port: <port>
fix(scripts): install/update/uninstall port handling
Three script-level port UX issues found and fixed:
== install.sh: re-install with PANEL_PORT now updates existing config ==
write_config previously returned early when config.yaml already existed,
ignoring PANEL_PORT env var. Re-running 'PANEL_PORT=9000 bash install.sh'
on an existing install silently kept the old port.
Fix: when config.yaml exists and PANEL_PORT/THREE_M_UI_PORT is explicitly
set, sed-update the port/listen/public_url in the existing file. First-
time install (no config.yaml) still writes full config with random keys.
== update.sh: show panel port after successful update ==
Update completed with no indication of which port the panel is on.
Users had to check config.yaml manually.
Fix: after '[5/5] Update completed', read server.port from config.yaml
and display:
Panel: http://SERVER_IP:<port>/
(to change port: 3m-ui config port <new-port>)
Also added CONFIG_DIR constant (was missing).
== uninstall.sh: show previous panel port before removing config ==
Uninstall removed config without telling the user what port was in use.
Fix: before rm -rf $CONFIG_DIR, read and display:
Previous panel port: <port>
fix(scripts): install/update/uninstall port handling
Three script-level port UX issues found and fixed:
== install.sh: re-install with PANEL_PORT now updates existing config ==
write_config previously returned early when config.yaml already existed,
ignoring PANEL_PORT env var. Re-running 'PANEL_PORT=9000 bash install.sh'
on an existing install silently kept the old port.
Fix: when config.yaml exists and PANEL_PORT/THREE_M_UI_PORT is explicitly
set, sed-update the port/listen/public_url in the existing file. First-
time install (no config.yaml) still writes full config with random keys.
== update.sh: show panel port after successful update ==
Update completed with no indication of which port the panel is on.
Users had to check config.yaml manually.
Fix: after '[5/5] Update completed', read server.port from config.yaml
and display:
Panel: http://SERVER_IP:<port>/
(to change port: 3m-ui config port <new-port>)
Also added CONFIG_DIR constant (was missing).
== uninstall.sh: show previous panel port before removing config ==
Uninstall removed config without telling the user what port was in use.
Fix: before rm -rf $CONFIG_DIR, read and display:
Previous panel port: <port>
fix(scripts): install/update/uninstall port handling
Three script-level port UX issues found and fixed:
== install.sh: re-install with PANEL_PORT now updates existing config ==
write_config previously returned early when config.yaml already existed,
ignoring PANEL_PORT env var. Re-running 'PANEL_PORT=9000 bash install.sh'
on an existing install silently kept the old port.
Fix: when config.yaml exists and PANEL_PORT/THREE_M_UI_PORT is explicitly
set, sed-update the port/listen/public_url in the existing file. First-
time install (no config.yaml) still writes full config with random keys.
== update.sh: show panel port after successful update ==
Update completed with no indication of which port the panel is on.
Users had to check config.yaml manually.
Fix: after '[5/5] Update completed', read server.port from config.yaml
and display:
Panel: http://SERVER_IP:<port>/
(to change port: 3m-ui config port <new-port>)
Also added CONFIG_DIR constant (was missing).
== uninstall.sh: show previous panel port before removing config ==
Uninstall removed config without telling the user what port was in use.
Fix: before rm -rf $CONFIG_DIR, read and display:
Previous panel port: <port>
fix(scripts): install/update/uninstall port handling
Three script-level port UX issues found and fixed:
== install.sh: re-install with PANEL_PORT now updates existing config ==
write_config previously returned early when config.yaml already existed,
ignoring PANEL_PORT env var. Re-running 'PANEL_PORT=9000 bash install.sh'
on an existing install silently kept the old port.
Fix: when config.yaml exists and PANEL_PORT/THREE_M_UI_PORT is explicitly
set, sed-update the port/listen/public_url in the existing file. First-
time install (no config.yaml) still writes full config with random keys.
== update.sh: show panel port after successful update ==
Update completed with no indication of which port the panel is on.
Users had to check config.yaml manually.
Fix: after '[5/5] Update completed', read server.port from config.yaml
and display:
Panel: http://SERVER_IP:<port>/
(to change port: 3m-ui config port <new-port>)
Also added CONFIG_DIR constant (was missing).
== uninstall.sh: show previous panel port before removing config ==
Uninstall removed config without telling the user what port was in use.
Fix: before rm -rf $CONFIG_DIR, read and display:
Previous panel port: <port>
fix(scripts): install/update/uninstall port handling
Three script-level port UX issues found and fixed:
== install.sh: re-install with PANEL_PORT now updates existing config ==
write_config previously returned early when config.yaml already existed,
ignoring PANEL_PORT env var. Re-running 'PANEL_PORT=9000 bash install.sh'
on an existing install silently kept the old port.
Fix: when config.yaml exists and PANEL_PORT/THREE_M_UI_PORT is explicitly
set, sed-update the port/listen/public_url in the existing file. First-
time install (no config.yaml) still writes full config with random keys.
== update.sh: show panel port after successful update ==
Update completed with no indication of which port the panel is on.
Users had to check config.yaml manually.
Fix: after '[5/5] Update completed', read server.port from config.yaml
and display:
Panel: http://SERVER_IP:<port>/
(to change port: 3m-ui config port <new-port>)
Also added CONFIG_DIR constant (was missing).
== uninstall.sh: show previous panel port before removing config ==
Uninstall removed config without telling the user what port was in use.
Fix: before rm -rf $CONFIG_DIR, read and display:
Previous panel port: <port>
Z User
dbec0b3099