After bitsocial update install installs a new version and restarts the previously-running daemon(s), the user loses access to the old daemon's stdout terminal (which contains the web UI links and other useful runtime output). The new daemon is spawned detached with stdio: "ignore", so the user has no easy way to discover those links from the parent terminal.
Proposal
After a successful install + restart, print:
To see the daemon logs run bitsocial logs --stdout
Conditions
- Only print when a new version was actually installed (skip when already on this version).
- Only print when daemons were running and got restarted — otherwise the message is misleading.
After
bitsocial update installinstalls a new version and restarts the previously-running daemon(s), the user loses access to the old daemon's stdout terminal (which contains the web UI links and other useful runtime output). The new daemon is spawned detached withstdio: "ignore", so the user has no easy way to discover those links from the parent terminal.Proposal
After a successful install + restart, print:
Conditions