Skip to content

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

Run many lanes on one machine

Use this when you keep many lanes on one machine and want the unused ones to cost little without stalling the ones that work in the background.

::example{slug="showcase-many-services"}

An unused lane is throttled, then frozen, and the next request brings it back (Throttling and freezing). Set both times in the user config; 0s turns either off.

~/.devlanes/config.yaml
lanes:
throttle_after: 10m
freeze_after: 1h

A worker or a queue consumer works without requests, so mark it, and its lane is never throttled or frozen while it runs.

devlanes.yaml
services:
worker:
run: node worker.mjs
keep_awake: true

Every start goes through a start gate that limits how many services start at once across all lanes. A fixed window keeps that number constant.

~/.devlanes/config.yaml
startup:
mode: fixed
max: 4

Logs share one age and size limit across all lanes. Data folders and the volumes of a lane’s own containers stay until the lane is cleaned, as Remove lanes shows.

~/.devlanes/config.yaml
logs:
retention:
days: 3
max_size: 2GiB

The daemon reads the user config when it starts, so restart it from a shell that has your services’ variables.

Terminal window
$ devlanes daemon restart

A browser tab whose dev client keeps sending over a WebSocket counts as use, and so does a busy watcher. Close the tab, or see Throttling and freezing for what else counts.