fix(install): close the four fresh-install-audit findings - #606
Merged
Conversation
From an outside-in fresh install of the repo on a clean host: - setup-env.sh 'NEXT:' hint now says 'docker compose pull && docker compose up -d', matching the README's two-command sequence instead of skipping pull. - setup-env.sh gains a middle 'advisory' free-space band: below 50 GiB (but above the 10 GiB hard floor) it now warns that the disk is small for continuous recording, so an 11-GiB path no longer passes silently. The doc (AI-INSTALL 1) promised this warning; the script now actually emits it. - AI-INSTALL: note that GET /auth/setup-status echoes 'localhost' for a host-local request, so a headless installer sets server_address to the real LAN address, not the suggestion. - README install section: note that HTTPS on :8443 uses an internal self-signed cert (browser warns on first visit); plain http on :8080 on a trusted LAN is fine. Points at docs/TLS.md. Validated: bash -n clean; the advisory band fires for 11 GiB and not for 60 GiB. Signed-off-by: badbread <badbread@users.noreply.github.com>
badbread
added a commit
that referenced
this pull request
Aug 9, 2026
Bring the [0.2.0] UNRELEASED section current with the final PRs merged after the previous changelog pass: the release version-drift guard (#605), the fresh-install-audit fixes (#606), the Android playback-wall intensity batching (#607), and the desktop-webview embedded-dropdown fix (#608). Added to Fixed and to All merged changes. Still UNRELEASED; dating the header is the release step. Signed-off-by: badbread <badbread@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
An outside-in fresh install (a fresh-context run following only the repo on a clean host) came back installable, no blockers. These four polish items close the friction it logged.
Medium
scripts/setup-env.sh'sNEXT:hint said onlydocker compose up -d, skipping the README's explicitdocker compose pull. Now printsdocker compose pull && docker compose up -dto match the README.docs/AI-INSTALL.md§1 says to warn on a small path. Added an advisory band: below 50 GiB (above the floor) it now notes the disk is small for continuous recording and to plan retention / use a larger disk. (Verified: fires at 11 GiB, silent at 60 GiB.)Nit
3.
docs/AI-INSTALL.md:GET /auth/setup-statusechoeslocalhostfor a host-local request; added a line so a headless installer setsserver_addressto the real LAN address rather than the suggestion.4.
README.mdinstall section: added a note that HTTPS on:8443uses an internal self-signed cert (browser warns on first visit), and that plainhttp://…:8080on a trusted LAN is fine, pointing atdocs/TLS.md.All install-surface files kept consistent (golden rule 5).
bash -nclean, no em-dashes, advisory logic unit-checked.