Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.codezero.io/llms.txt

Use this file to discover all available pages before exploring further.

Print the environment variables a consumer needs to route traffic through cordon. Use the output in your shell, .envrc (direnv), .mise.toml, or any tooling that consumes env vars.

​
Usage

cordon env [OPTIONS]

​
Options

OptionDescription
--scopeConfiguration scope: project (default) or user
--config, -cPath to cordon.toml (overrides scope-resolved path)
--formatOutput format: shell (default), fish, dotenv, json
Unlike most config-reading commands, --config does not conflict with --scope; when provided, --config wins.

​
Examples

Interactive shell (bash / zsh): 
eval "$(cordon env)"
fish: 
cordon env --format fish | source
direnv (.envrc): 
eval "$(cordon env)"
mise (.mise.toml): 
cordon env --format dotenv > .mise.cordon.env
JSON for scripting: 
cordon env --format json | jq .HTTPS_PROXY

​
Output

Vars emitted:
  • HTTPS_PROXY / HTTP_PROXY (plus lowercase) — http://<audience>:<token>@127.0.0.1:<port> when token enforcement is active, otherwise http://127.0.0.1:<port> with a warning. <audience> is Cordon’s local scope namespace, not an OAuth/OIDC audience claim.
  • NODE_EXTRA_CA_CERTS — absolute path to the Cordon CA cert. Node.js expects a raw cert, not a bundle.
  • SSL_CERT_FILE / REQUESTS_CA_BUNDLE / CURL_CA_BUNDLE — absolute path to the combined (system + Cordon) CA bundle. These env vars replace the default trust store, so a bundle is required.
  • JSON output is a flat object of environment variable names to string values, preserving compatibility with scripts that export every top-level entry.
Authenticated proxy URLs contain Cordon tokens. Do not commit or share them. See Proxy Tokens for rotation and handling guidance.
See the generic tool guide for where to apply these values and SDK Compatibility for runtime-specific exceptions.

​
Errors

  • no cordon.toml at <path> — run \cordon setup` first` — no config at the resolved scope path.
  • Bundle vars are omitted (with a comment) if combined-ca.pem is missing; run cordon setup to generate it.

​
See also