Skip to content

chore: remove Cloudflare Access section from public docs #68

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
suisuss merged 1 commit into from
May 12, 2026
Merged

chore: remove Cloudflare Access section from public docs #68

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 0 additions & 20 deletions docs/concepts.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,26 +26,6 @@ Run `kh auth login` to authenticate via browser OAuth. For headless environments

Run `kh auth status` to see which method is active and whether your token is valid.

## Gated Environments (Cloudflare Access)

Hosts behind Cloudflare Access (PR previews, staging) require additional credentials on every request. The CLI sends them as headers from two sources:

1. **Environment variables** (precedence: env > hosts.yml):
- `CF_ACCESS_CLIENT_ID` + `CF_ACCESS_CLIENT_SECRET` -- service-token pair, sent as `CF-Access-Client-Id` / `CF-Access-Client-Secret`. Both must be set; partial values are ignored.
- `CF_AUTHORIZATION` -- the `cf_authorization` JWT minted by `cloudflared access login`, sent as `Cookie: CF_Authorization=<value>`.
2. **Per-host `headers:` map in `hosts.yml`** -- arbitrary headers attached to every request to that host:

```yaml
hosts:
app-pr-1234.keeperhub.com:
token: kh_prte_...
headers:
CF-Access-Client-Id: <id>
CF-Access-Client-Secret: <secret>
```

Use env vars in CI; use `hosts.yml` for stable per-environment config that follows your machine.

## Output Formats

By default, most commands render a human-readable table. Use these flags for machine-readable output:
Expand Down
Loading