feat: add COLLIE_SKIP_SERVE to bypass tailscale serve#13
Closed
diogenesc wants to merge 1 commit into
Closed
Conversation
Adds COLLIE_SKIP_SERVE=1 support to collie-ctl.sh so the bridge can run behind a reverse proxy (Caddy, Nginx, etc.) without triggering tailscale serve. The bridge stays on 127.0.0.1 only — your proxy handles TLS, auth, and public access. - cmd_serve/cmd_unserve: early return when COLLIE_SKIP_SERVE=1 - print_status_banner: shows 'proxy' instead of 'tailnet' when skipped - cmd_status: skips tailscale serve status check when skipped - .env.example: documents the new variable - Version bumped to 0.12.0 (minor — new feature)
5 tasks
Owner
|
Thanks @diogenesc! this is a use case I want to support properly, so I picked it up into #14 and bundled the security-docs changes it needed; your commit rides along there. It'll close this PR when it lands. Appreciate it 🙏 |
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
2 participants
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.
Summary
Adds
COLLIE_SKIP_SERVE=1env var to skiptailscale serveentirely. The bridge stays on loopback only (or0.0.0.0ifCOLLIE_HOSTis set), ideal for deployments behind a reverse proxy (Caddy, Nginx, etc.) or direct port access via MagicDNS.Changes
scripts/collie-ctl.sh:cmd_serve(),cmd_unserve(),cmd_status(), andprint_status_banner()all respectCOLLIE_SKIP_SERVE=1.env.example: documents the new variableUse case
When running Collie behind Caddy/Nginx or accessing directly via
http://host:port, there's no need fortailscale serve— your proxy handles TLS, auth, and public access. This avoids the bridge fighting over the tailscale serve mapping.