Skip to content

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

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 as api.acme2.localhost resolve to this machine: the strategy (resolver), its tld, 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 every hosts entry, and whether other devices on the network may connect to it.
  • remote: Settings for devlanes remote connect: boxes reached by a command, and how this machine serves clients when it is a box.
  • start: What a plain devlanes 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 with progress (the tab’s progress bar during starts).
  • tls: Which certificate authority signs the proxy’s HTTPS certificates (ca), and which stores devlanes setup installs 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).
~/.devlanes/config.yaml
hostnames:
resolver: localhost
ports:
range: 20000-32767
terminal:
progress: auto