Skip to content

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

Environment variables

devlanes sets variables in the processes it starts, and reads a few that you set. The order in which a unit’s variables are layered, and which layer wins, is on Environment and expressions.

Services, tasks, and infra.setup and infra.teardown entries get these.

VariableValue
DEVLANES1.
DEVLANES_CA_BUNDLEThe path of ~/.devlanes/ca/bundle.pem: the system’s roots and the devlanes root in one file.
DEVLANES_CA_CERTThe path of the devlanes root certificate: ~/.devlanes/ca/ca.pem, or mkcert’s rootCA.pem with tls.ca: mkcert.
DEVLANES_CA_TRUSTSTOREThe path of ~/.devlanes/ca/truststore.p12: the certificates of DEVLANES_CA_BUNDLE as a PKCS#12 trust store with the password changeit. Not set when devlanes could not write it; devlanes doctor says why.
DEVLANES_LANEThe lane number: 0, 1, 2 and so on.
DEVLANES_LANE_DATAThe path of the lane data folder.
DEVLANES_LANE_NAMEmain for lane 0, lane<N> for lane N.
DEVLANES_LANE_PROJECTproject from the project file, such as myapp. devlanes commands run by the unit use this project.
VariableValue
DEVLANES_ORIGINSThe lane’s origins, separated by commas: https:// and each hostname of each service, then http://localhost:<port> and http://127.0.0.1:<port> for each service.
DEVLANES_SERVICEThe service name from the project file.
HOST127.0.0.1.
PORTThe service’s port.
RuntimeVariableValue
Node, BunNODE_EXTRA_CA_CERTSThe path in DEVLANES_CA_CERT.
DenoDENO_CERTThe path in DEVLANES_CA_CERT.
PythonSSL_CERT_FILE, REQUESTS_CA_BUNDLEThe path in DEVLANES_CA_BUNDLE.
RustSSL_CERT_FILEThe path in DEVLANES_CA_BUNDLE.
GoSSL_CERT_FILEThe path in DEVLANES_CA_BUNDLE.
JavaJAVA_TOOL_OPTIONSThe value from the shell, mise or direnv, followed by -Djavax.net.ssl.trustStore=<the path in DEVLANES_CA_TRUSTSTORE> -Djavax.net.ssl.trustStoreType=PKCS12 -Djavax.net.ssl.trustStorePassword=changeit. Left as it is when it already sets javax.net.ssl.trustStore.

devlanes exec, devlanes with and devlanes env shell give the command the lane’s variables: the ones for every unit, the runtime variables above that your shell does not set, JAVA_TOOL_OPTIONS composed onto your shell’s value, the global_env and profile env entries that read neither self nor replica, and one variable per service:

VariableValue
DEVLANES_PUBLIC_URL_<SERVICE>The service’s public_url, or its url when it has no hostname. <SERVICE> is the service name in uppercase with each other character replaced by _: crm-api gives DEVLANES_PUBLIC_URL_CRM_API.
VariableValuesEffect
CLICOLOR_FORCEAny value except empty and 0.Color in output that does not go to a terminal.
DEVLANES_AGENT0The command counts as a person’s, even when a coding agent runs it.
DEVLANES_HOMEA path.The devlanes home, instead of ~/.devlanes. Each home has its own daemon.
DEVLANES_INSTALL_DIRA folder.Where install.sh and install.ps1 install.
DEVLANES_LOGA level such as debug. Default info.The level of the daemon’s log, read when the daemon starts.
DEVLANES_NO_UIAny value except empty and 0.A start on a terminal prints its progress instead of opening the TUI, as --no-ui does.
DEVLANES_NO_UPDATE_CHECKAny value except empty, 0 and false.Turns the release check off.
DEVLANES_OUTPUThuman, plain, agent or json.The output mode, unless --output or --json is given.
DEVLANES_PROJECTA project name.The same as --project.
DEVLANES_SHELL_ENV0 or 1; pwsh or powershell on Windows.Whether devlanes mcp reads your login shell’s environment (MCP tools).
DEVLANES_TERM_LINKS, DEVLANES_TERM_MARKS, DEVLANES_TERM_NOTIFICATIONS, DEVLANES_TERM_PROGRESS, DEVLANES_TERM_TITLE0 or 1.Turns off or on the terminal feature of the same name under terminal in the user config.
DEVLANES_VERBOSE1 or 2.The same as -v or -vv.
NO_COLORAny value except empty.No color.

A daemon that a command starts keeps only these variables of that command’s shell: PATH, HOME, USER, LOGNAME, SHELL, LANG, TZ, TMPDIR, TERM, SSH_AUTH_SOCK, KUBECONFIG, the proxy variables such as HTTPS_PROXY, the CI markers such as CI, and those that start with LC_, XDG_, DOCKER_ or DEVLANES_. On Windows it also keeps the system’s own variables, such as USERPROFILE, APPDATA and TEMP. Each unit gets the environment of the command that started it.