User file reference
Top-level keys of ~/.devlanes/config.yaml. Each has a page with every key under it.
daemon: The daemon’s lifetime: whether it stops on its own once nothing runs and no TUI is open.history: How long the database keeps records of finished service and task runs, and of remote boxes that no longer connect.hostnames: How lane hostnames such asapi.acme2.localhostresolve to this machine: the strategy (resolver), itstld, and whether names also go into/etc/hosts(hosts_file).lanes: Where lane data folders (lane.data_path) live on this machine, and how long a lane may sit without activity before devlanes throttles or freezes it.logs: How much service output devlanes keeps under~/.devlanes/logs, by age and total size.metrics: How long CPU and memory history stays in the daemon’s database.ports: Port range that every lane of every project takes its block of ports from, so lanes never collide.proxy: Ports of the daemon’s HTTP/HTTPS proxy, which serves everyhostsentry, and whether other devices on the network may connect to it.remote: Settings fordevlanes remote connect: boxes reached by a command, and how this machine serves clients when it is a box.start: What a plaindevlanes start(no services, no--profile) brings up: the services the lane ran before, or its default selection.startup: How many services may be starting at the same time across all lanes and projects, so a large start does not overload the machine.state: Size budget for the daemon’s database; past it, the oldest metrics and history are deleted before their retention ends.terminal: Terminal integration of the CLI, written as a mapping withprogress(the tab’s progress bar during starts).tls: Which certificate authority signs the proxy’s HTTPS certificates (ca), and which storesdevlanes setupinstalls it into (trust).tui: Whether start commands open the terminal UI, how it looks, and what quitting it does with running lanes.updates: Release checks: whether the daemon looks for newer devlanes releases (mode), and whether the TUI shows release highlights after an update (highlights).
hostnames: resolver: localhostports: range: 20000-32767terminal: progress: autohostnamesHow lane hostnames such as api.acme2.localhost resolve to this machine: the strategy (resolver), its tld, and whether names also go into /etc/hosts (hosts_file). The defaults need no setup for browsers that resolve *.localhost.
hostnames.resolverWhich domain lanes get and what makes their hostnames resolve; defaults to localhost. resolver also needs tld and a one-time devlanes setup; public is not supported yet.
portsPort range that every lane of every project takes its block of ports from, so lanes never collide. Defaults to 20000-32767.
ports.rangePorts devlanes may hand out, written start-end (both included, start above 0); defaults to 20000-32767, below Linux's usual ephemeral range so the OS does not pick them for outgoing connections. Each lane of each project gets its own block of consecutive ports from it, so a smaller range fits fewer lanes.
terminalTerminal integration of the CLI, written as a mapping with progress (the tab's progress bar during starts). A plain string, the terminal app name older versions used, is still accepted but ignored with a warning.
terminal.progressWhether starts show their progress in the terminal tab's own progress bar (the OSC 9;4 sequence); defaults to auto. Only human output on a terminal gets it, and DEVLANES_TERM_PROGRESS=0 or 1 overrides this setting.