gsxdsm 2f8d2e8ee0 feat: add scripts/run-container.sh for launching the Fusion container ...

The correct `docker run` is long and every piece of it fails confusingly when
omitted: the OAuth callback ports are fixed by the providers' registered redirect
URIs and unreachable without PI_OAUTH_CALLBACK_HOST=0.0.0.0, /home/node must be a
volume or the Tailscale login and embedded Postgres are lost on recreate, and
--tailscale is an entrypoint flag that must precede the CLI arguments.

- Every knob is an environment variable, so per-container config lives in an
  --env-file outside the repo rather than a committed token.
- FUSION_STATE_VOLUME supports setups that mount /home/node/.fusion as its own
  volume nested inside /home/node; omitting it is not destructive but silently
  points the dashboard at a different database, so the board comes up empty.
- An existing container is never replaced without --recreate, and volumes are
  never removed, so a recreate keeps the database, settings, and tailnet login.
- --dry-run prints the command without running it, including when the container
  already exists, which is exactly when previewing a recreate is most useful.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2026-08-22 19:21:31 -07:00

7.0 KiB

Executable File

Raw Blame History

View Raw