Skip to content

fix(install): hint flue restart when updating - #119

Merged
karngyan merged 1 commit into
mainfrom
worktree-install-update-restart-hint
Aug 19, 2026
Merged

fix(install): hint flue restart when updating#119
karngyan merged 1 commit into
mainfrom
worktree-install-update-restart-hint

Conversation

@karngyan

Copy link
Copy Markdown
Contributor

What

install.sh closes with next: flue enable unconditionally, but the same script serves updates over an existing install. After an update the running daemon keeps executing the old build until it is restarted, so flue enable (which deliberately never restarts a healthy daemon) is the wrong hint.

How

  • Before the new binary lands, the script checks for an executable at ${INSTALL_DIR}/flue. If one is there, the run is an update and the closing hint becomes next: flue restart. Fresh installs keep next: flue enable.
  • The detection happens before install_binary, otherwise every install would look like an update. The dry-run path prints the same hint.

Tests

  • New case in scripts/install_test.sh: a dry-run against an install dir that already holds an executable flue must end with next: flue restart and must not mention flue enable. Watched it fail before the fix.
  • bash scripts/install_test.sh: all 23 assertions pass.
  • shellcheck scripts/install.sh scripts/install_test.sh: clean.

🤖 Generated with Claude Code

install.sh serves first installs and updates alike. After an update
the daemon keeps running the old build until restarted, so the
closing hint must say restart, not enable, when a flue binary
already sits at the install path.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@karngyan
karngyan merged commit 0ba0f49 into main Aug 19, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant