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).
tls: ca: devlanes trust: - system - firefoxtlsWhich certificate authority signs the proxy's HTTPS certificates (ca), and which stores devlanes setup installs it into (trust).
tls.caWhich CA signs the certificate for each lane hostname; defaults to devlanes. Choose mkcert when your browsers already trust mkcert's CA.
tls.trustStores 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.
tls.ca
Section titled “tls.ca”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/caon first use, limited to names underlocalhost,test,internal,home.arpaandhostnames.tld, so it cannot sign for real sites. Trust it once withdevlanes setup.mkcert: Load mkcert’s existing root CA (frommkcert -CAROOT) instead, so browsers that already trust it need nothing new. HTTPS stays off whenmkcertis not onPATH; the mkcert CA has no name limits, anddevlanes setup --removeleaves it trusted.
tls: ca: devlanestlsWhich certificate authority signs the proxy's HTTPS certificates (ca), and which stores devlanes setup installs it into (trust).
tls.caWhich CA signs the certificate for each lane hostname; defaults to devlanes. Choose mkcert when your browsers already trust mkcert's CA.
tls.trust
Section titled “tls.trust”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, throughcertutilfrom the NSS tools (brew install nss, orlibnss3-tools/nss-toolson Linux).chrome: The store Chrome and Chromium read:~/.pki/nssdbthroughcertutilon Linux, the same login keychain assystemon 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.exethrough interop, and Windows asks you to confirm each change. On Windows it is the same store assystem; on macOS and Linux outside WSLdevlanes setupreports 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.
tls: trust: - system - firefoxtlsWhich certificate authority signs the proxy's HTTPS certificates (ca), and which stores devlanes setup installs it into (trust).
tls.trustStores 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.