Skip to content

devlanes is in beta and not ready for production use.Report an issue

tls in config.yaml

A top-level key of ~/.devlanes/config.yaml.

Type: mapping.

Which certificate authority signs the proxy’s HTTPS certificates (ca), and which stores devlanes setup installs it into (trust).

~/.devlanes/config.yaml
tls:
ca: devlanes
trust:
- system
- firefox

Type: string. Default: devlanes.

Which CA signs the certificate for each lane hostname; defaults to devlanes. Choose mkcert when your browsers already trust mkcert’s CA.

Values:

  • devlanes: devlanes creates its own CA in ~/.devlanes/ca on first use, limited to names under localhost, test, internal, home.arpa and hostnames.tld, so it cannot sign for real sites. Trust it once with devlanes setup.
  • mkcert: Load mkcert’s existing root CA (from mkcert -CAROOT) instead, so browsers that already trust it need nothing new. HTTPS stays off when mkcert is not on PATH; the mkcert CA has no name limits, and devlanes setup --remove leaves it trusted.
~/.devlanes/config.yaml
tls:
ca: devlanes

Type: list of strings.

Stores devlanes setup installs the CA into and devlanes setup --remove removes it from; an empty list means [system]. On Linux, browsers do not read the system store, so add chrome and firefox there; inside WSL add windows for browsers on Windows. devlanes doctor shows each store’s state.

Each item: Certificate store that devlanes setup installs the CA into.

Values:

  • system: The OS store: the login keychain on macOS, read by Safari, Chrome, Edge and /usr/bin/curl; on Linux, the distribution’s CA anchors, updated through sudo.
  • firefox: Every Firefox profile’s certificate database, through certutil from the NSS tools (brew install nss, or libnss3-tools / nss-tools on Linux).
  • chrome: The store Chrome and Chromium read: ~/.pki/nssdb through certutil on Linux, the same login keychain as system on macOS.
  • windows: The Windows user root store, read by Edge, Chrome and Firefox on Windows. For devlanes inside WSL, whose browser usually runs on Windows: it runs Windows’ certutil.exe through interop, and Windows asks you to confirm each change. On Windows it is the same store as system; on macOS and Linux outside WSL devlanes setup reports it as unavailable.
  • ios-simulator: Reserved for the iOS simulator; not supported yet, so it is dropped with a warning.
  • android-emulator: Reserved for the Android emulator; not supported yet, so it is dropped with a warning.
~/.devlanes/config.yaml
tls:
trust:
- system
- firefox