Skip to content

docs: LAN exposure goes through HOST_BIND_ADDRESS in .env (issue #56) - #65

Merged
SebConejo merged 3 commits into
mainfrom
fix/issue-56-lan-exposure
Aug 18, 2026
Merged

docs: LAN exposure goes through HOST_BIND_ADDRESS in .env (issue #56)#65
SebConejo merged 3 commits into
mainfrom
fix/issue-56-lan-exposure

Conversation

@SebConejo

@SebConejo SebConejo commented Aug 15, 2026

Copy link
Copy Markdown
Member

Applies option 1 of #56 (batch pass, 2026-08-15):

  • The "Exposing on the LAN" steps set HOST_BIND_ADDRESS=0.0.0.0 in .env instead of editing a compose line that no longer exists (and whose hand-edit is wiped by install.sh --upgrade).
  • The page's Core env-var table gains the HOST_BIND_ADDRESS row and the BIND_ADDRESS note re-points to it.
  • The environment-variables reference gains the matching row (never-halfway rule; consumes the backlog line).

Coherence: GREEN (now 57 vars). Closes #56.

The compose ports line the page told users to edit no longer exists,
and any hand-edit is wiped by install.sh --upgrade. The steps now set
HOST_BIND_ADDRESS=0.0.0.0 in .env; the page's Core table and the
environment-variables reference gain the matching row, and the
BIND_ADDRESS note points at the right knob.
The template syntax explanation goes; the instruction and the
upgrade-survival warning stay. Same trim on the reference row. Also
merges main.
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.

Docs audit — self-hosting with Docker — 2026-08-12

1 participant