detached 091af1a

docs(cli): clarify tailscale admin TLS with wildcard DNS routing

commit
091af1a8f194768eabf05613346c6fcbf80ea02c
author
brice · · 2026-02-06 19:42 UTC
committer
brice · · 2026-02-06 19:42 UTC
parent
8b57a60
signature
unsigned
2 files · +28 -0
M docs/cli/index.md +2 -0
@@ -122,6 +122,8 @@ when you want to bypass your saved configuration.
122122 Use `--insecure` when the remote endpoint uses a self-signed or otherwise untrusted TLS certificate.
123123 You can make this persistent with `insecure_tls = true` in `[client]` of `~/.config/gordon/gordon.toml`
124124 or in a specific entry in `~/.config/gordon/remotes.toml`.
125+This is useful when admin/API access goes through a private network (for example Tailscale),
126+while your public app domains still use wildcard DNS and normal reverse-proxy routing.
125127
126128 ```bash
127129 # Using flags (use the gordon_domain from remote Gordon config)
@@ -122,6 +122,8 @@ when you want to bypass your saved configuration.
122 Use `--insecure` when the remote endpoint uses a self-signed or otherwise untrusted TLS certificate.122 Use `--insecure` when the remote endpoint uses a self-signed or otherwise untrusted TLS certificate.
123 You can make this persistent with `insecure_tls = true` in `[client]` of `~/.config/gordon/gordon.toml`123 You can make this persistent with `insecure_tls = true` in `[client]` of `~/.config/gordon/gordon.toml`
124 or in a specific entry in `~/.config/gordon/remotes.toml`.124 or in a specific entry in `~/.config/gordon/remotes.toml`.
125+This is useful when admin/API access goes through a private network (for example Tailscale),
126+while your public app domains still use wildcard DNS and normal reverse-proxy routing.
125 127
126 ```bash128 ```bash
127 # Using flags (use the gordon_domain from remote Gordon config)129 # Using flags (use the gordon_domain from remote Gordon config)
M docs/cli/remotes.md +26 -0
@@ -304,6 +304,32 @@ gordon remotes use prod && gordon routes list
304304 gordon remotes use staging && gordon routes list
305305 ```
306306
307+### Tailscale Admin + Wildcard App Domains
308+
309+Use this pattern when Gordon admin/API is reachable only on a Tailscale path (self-signed or private cert),
310+while app traffic still uses your public wildcard DNS and reverse-proxy routing.
311+
312+```toml
313+# ~/.config/gordon/remotes.toml
314+active = "prod-ts"
315+
316+[remotes.prod-ts]
317+url = "https://gordon-backend.tailnet.ts.net"
318+token_env = "GORDON_TOKEN"
319+insecure_tls = true
320+```
321+
322+```bash
323+# CLI calls Gordon admin API over Tailscale with insecure TLS allowed
324+gordon status
325+gordon routes list
326+gordon deploy app.bnema.dev
327+```
328+
329+`insecure_tls` only affects CLI -> Gordon admin HTTPS verification. It does not change
330+your runtime routing: the Gordon reverse proxy and container routes can still serve
331+`*.bnema.dev` behind your normal wildcard DNS setup.
332+
307333 ## Related
308334
309335 - [CLI Overview](./index.md)
@@ -304,6 +304,32 @@ gordon remotes use prod && gordon routes list
304 gordon remotes use staging && gordon routes list304 gordon remotes use staging && gordon routes list
305 ```305 ```
306 306
307+### Tailscale Admin + Wildcard App Domains
308+
309+Use this pattern when Gordon admin/API is reachable only on a Tailscale path (self-signed or private cert),
310+while app traffic still uses your public wildcard DNS and reverse-proxy routing.
311+
312+```toml
313+# ~/.config/gordon/remotes.toml
314+active = "prod-ts"
315+
316+[remotes.prod-ts]
317+url = "https://gordon-backend.tailnet.ts.net"
318+token_env = "GORDON_TOKEN"
319+insecure_tls = true
320+```
321+
322+```bash
323+# CLI calls Gordon admin API over Tailscale with insecure TLS allowed
324+gordon status
325+gordon routes list
326+gordon deploy app.bnema.dev
327+```
328+
329+`insecure_tls` only affects CLI -> Gordon admin HTTPS verification. It does not change
330+your runtime routing: the Gordon reverse proxy and container routes can still serve
331+`*.bnema.dev` behind your normal wildcard DNS setup.
332+
307 ## Related333 ## Related
308 334
309 - [CLI Overview](./index.md)335 - [CLI Overview](./index.md)

Keyboard shortcuts

Single-key shortcuts are on. ctrl k and esc work whatever this says.

ctrl k :
go to a section, branch, tag, file or repository
?
this list
j k
move the row cursor down / up
enter
open the row under the cursor; on Files, a directory opens or closes in place
↑ ↓ ← → home end
in the file tree (focus on a row): previous / next row, close / open a directory or go to its parent / first entry, first / last row. They never open a file
l h
on Files: open a directory or a file / close a directory or go up to its parent, then to the parent page. Elsewhere: into the side panel (on a merge request, its files) / back to the content; there j k move between its controls
g g G
first / last row
/
filter the list; on Files, find a file anywhere in the repository (esc clears, enter opens the best match)
b
switch branch or tag
g s g f g c g b g m g i g r g a
tabs: summary, files, commits, branches & tags, merge requests, issues, releases, actions (when available)
g h
home
w
wide mode: use the whole width of the screen, or not (remembered)
y
copy a permalink pinned to the commit
d u x
diff: split / unified / collapse or expand all
e E
diff: the whole file in view / every file, with the lines the hunks hide
n
merge request: next note in the diff
esc
close a dialog, leave a field

Branches 7

Tags 106

↑↓ moveenter openesc close