infra in devlanes.yaml
A top-level key of devlanes.yaml.
Type: mapping.
Containers the lanes depend on (databases, brokers, object stores), started and waited on before setup, tasks and services, plus the commands that create and remove each lane’s data in them.
infra: compose: docker-compose.yml hidden: - postgresinfraContainers the lanes depend on (databases, brokers, object stores), started and waited on before setup, tasks and services, plus the commands that create and remove each lane's data in them.
Config referenceinfra.composeCompose file, or a list of files merged like repeated -f, relative to the project. Its services are shared by every lane unless listed in per_lane; the shared project runs from the primary worktree with the .env next to the project file there as --env-file.
infra.hiddenContainers that machines connected with devlanes remote connect never see, mirror or reach.
infra.compose
Section titled “infra.compose”Type: string or list of strings.
Compose file, or a list of files merged like repeated -f, relative to the project. Its services are shared by every lane unless listed in per_lane; the shared project runs from the primary worktree with the .env next to the project file there as --env-file.
infra: compose: docker-compose.ymlinfraContainers the lanes depend on (databases, brokers, object stores), started and waited on before setup, tasks and services, plus the commands that create and remove each lane's data in them.
Config referenceinfra.composeCompose file, or a list of files merged like repeated -f, relative to the project. Its services are shared by every lane unless listed in per_lane; the shared project runs from the primary worktree with the .env next to the project file there as --env-file.
infra.containers
Section titled “infra.containers”Type: mapping of names to mappings.
Docker containers run without a Compose file, keyed by name and reached as infra.<name> in expressions.
infra: containers: cerbos: image: ghcr.io/cerbos/cerbos:0.40.0 per_lane: true ports: http: 3592infraContainers the lanes depend on (databases, brokers, object stores), started and waited on before setup, tasks and services, plus the commands that create and remove each lane's data in them.
Config referenceinfra.containersDocker containers run without a Compose file, keyed by name and reached as infra.<name> in expressions.
infra.containers.<name>Docker container run without a Compose file, shared by every lane or one per lane. Processes reach it through ${{ infra.<name>.ports.<port> }}.
infra.containers.<name>.imageImage to run. Required. A running container with the same image, command, env, mounts and ports is reused; any change recreates it.
Config referenceinfra.containers.<name>.per_laneRun one container per lane instead of one shared by every lane. Defaults to false. Per-lane containers and their named volumes are removed by devlanes lane clean.
infra.containers.<name>.portsContainer ports by name. devlanes publishes each on a host port on 127.0.0.1, read as ${{ infra.<name>.ports.<port> }}; infra.<name>.port is the first one.
infra.containers.<name>.ports.<name>Container ports by name. devlanes publishes each on a host port on 127.0.0.1, read as ${{ infra.<name>.ports.<port> }}; infra.<name>.port is the first one.
infra.containers.<name>
Section titled “infra.containers.<name>”Type: mapping.
Docker container run without a Compose file, shared by every lane or one per lane. Processes reach it through ${{ infra.<name>.ports.<port> }}.
infra: containers: cerbos: image: ghcr.io/cerbos/cerbos:0.40.0 per_lane: true ports: grpc: 3593 http: 3592infraContainers the lanes depend on (databases, brokers, object stores), started and waited on before setup, tasks and services, plus the commands that create and remove each lane's data in them.
Config referenceinfra.containersDocker containers run without a Compose file, keyed by name and reached as infra.<name> in expressions.
infra.containers.<name>Docker container run without a Compose file, shared by every lane or one per lane. Processes reach it through ${{ infra.<name>.ports.<port> }}.
infra.containers.<name>.imageImage to run. Required. A running container with the same image, command, env, mounts and ports is reused; any change recreates it.
Config referenceinfra.containers.<name>.per_laneRun one container per lane instead of one shared by every lane. Defaults to false. Per-lane containers and their named volumes are removed by devlanes lane clean.
infra.containers.<name>.portsContainer ports by name. devlanes publishes each on a host port on 127.0.0.1, read as ${{ infra.<name>.ports.<port> }}; infra.<name>.port is the first one.
infra.containers.<name>.ports.<name>Container ports by name. devlanes publishes each on a host port on 127.0.0.1, read as ${{ infra.<name>.ports.<port> }}; infra.<name>.port is the first one.
infra.containers.<name>.command
Section titled “infra.containers.<name>.command”Type: string, list of strings or an expression.
Command replacing the image’s default: a list is used as is, a string runs through /bin/sh -c inside the container. In a list, an item that is one ${{ }} expression giving a number or true/false becomes its text, such as --port followed by ${{ self.port }}.
infra: containers: cerbos: command: - server - --config=/policies/config.yamlinfraContainers the lanes depend on (databases, brokers, object stores), started and waited on before setup, tasks and services, plus the commands that create and remove each lane's data in them.
Config referenceinfra.containersDocker containers run without a Compose file, keyed by name and reached as infra.<name> in expressions.
infra.containers.<name>Docker container run without a Compose file, shared by every lane or one per lane. Processes reach it through ${{ infra.<name>.ports.<port> }}.
infra.containers.<name>.commandCommand replacing the image's default: a list is used as is, a string runs through /bin/sh -c inside the container. In a list, an item that is one ${{ }} expression giving a number or true/false becomes its text, such as --port followed by ${{ self.port }}.
infra.containers.<name>.env
Section titled “infra.containers.<name>.env”Type: mapping of names to strings, booleans, numbers or expressions.
Environment variables set inside the container.
infra: containers: cerbos: env: LOG_LEVEL: debuginfraContainers the lanes depend on (databases, brokers, object stores), started and waited on before setup, tasks and services, plus the commands that create and remove each lane's data in them.
Config referenceinfra.containersDocker containers run without a Compose file, keyed by name and reached as infra.<name> in expressions.
infra.containers.<name>Docker container run without a Compose file, shared by every lane or one per lane. Processes reach it through ${{ infra.<name>.ports.<port> }}.
infra.containers.<name>.image
Section titled “infra.containers.<name>.image”Type: string or an expression.
Image to run. Required. A running container with the same image, command, env, mounts and ports is reused; any change recreates it.
infra: containers: cerbos: image: ghcr.io/cerbos/cerbos:0.40.0infraContainers the lanes depend on (databases, brokers, object stores), started and waited on before setup, tasks and services, plus the commands that create and remove each lane's data in them.
Config referenceinfra.containersDocker containers run without a Compose file, keyed by name and reached as infra.<name> in expressions.
infra.containers.<name>Docker container run without a Compose file, shared by every lane or one per lane. Processes reach it through ${{ infra.<name>.ports.<port> }}.
infra.containers.<name>.imageImage to run. Required. A running container with the same image, command, env, mounts and ports is reused; any change recreates it.
Config referenceinfra.containers.<name>.per_lane
Section titled “infra.containers.<name>.per_lane”Type: boolean or an expression.
Run one container per lane instead of one shared by every lane. Defaults to false. Per-lane containers and their named volumes are removed by devlanes lane clean.
infra: containers: cerbos: per_lane: trueinfraContainers the lanes depend on (databases, brokers, object stores), started and waited on before setup, tasks and services, plus the commands that create and remove each lane's data in them.
Config referenceinfra.containersDocker containers run without a Compose file, keyed by name and reached as infra.<name> in expressions.
infra.containers.<name>Docker container run without a Compose file, shared by every lane or one per lane. Processes reach it through ${{ infra.<name>.ports.<port> }}.
infra.containers.<name>.per_laneRun one container per lane instead of one shared by every lane. Defaults to false. Per-lane containers and their named volumes are removed by devlanes lane clean.
infra.containers.<name>.ports
Section titled “infra.containers.<name>.ports”Type: mapping of names to integers or expressions.
Container ports by name. devlanes publishes each on a host port on 127.0.0.1, read as ${{ infra.<name>.ports.<port> }}; infra.<name>.port is the first one.
infra: containers: cerbos: ports: grpc: 3593 http: 3592infraContainers the lanes depend on (databases, brokers, object stores), started and waited on before setup, tasks and services, plus the commands that create and remove each lane's data in them.
Config referenceinfra.containersDocker containers run without a Compose file, keyed by name and reached as infra.<name> in expressions.
infra.containers.<name>Docker container run without a Compose file, shared by every lane or one per lane. Processes reach it through ${{ infra.<name>.ports.<port> }}.
infra.containers.<name>.portsContainer ports by name. devlanes publishes each on a host port on 127.0.0.1, read as ${{ infra.<name>.ports.<port> }}; infra.<name>.port is the first one.
infra.containers.<name>.ports.<name>Container ports by name. devlanes publishes each on a host port on 127.0.0.1, read as ${{ infra.<name>.ports.<port> }}; infra.<name>.port is the first one.
infra.containers.<name>.ready
Section titled “infra.containers.<name>.ready”Type: started or mapping.
Extra check the start waits for once the container is up (the image’s healthcheck, else its first port accepting TCP), before setup, tasks and services run. Write started or one of tcp, http, log (matched against the container’s logs) or cmd (run on the host). If it does not pass within its timeout (default 60s), the start fails.
Takes the same values and keys as services.<name>.ready.
infra: containers: cerbos: ready: startedinfraContainers the lanes depend on (databases, brokers, object stores), started and waited on before setup, tasks and services, plus the commands that create and remove each lane's data in them.
Config referenceinfra.containersDocker containers run without a Compose file, keyed by name and reached as infra.<name> in expressions.
infra.containers.<name>Docker container run without a Compose file, shared by every lane or one per lane. Processes reach it through ${{ infra.<name>.ports.<port> }}.
infra.containers.<name>.readyExtra check the start waits for once the container is up (the image's healthcheck, else its first port accepting TCP), before setup, tasks and services run. Write started or one of tcp, http, log (matched against the container's logs) or cmd (run on the host). If it does not pass within its timeout (default 60s), the start fails.
infra.containers.<name>.volumes
Section titled “infra.containers.<name>.volumes”Type: list of strings or expressions.
Mounts as source:destination[:mode]. ./relative and /absolute sources are bind mounts; relative ones start at the project file’s directory, in the lane’s worktree for a per_lane container and in the primary worktree for a shared one. A bare name is a named volume kept per project or per lane.
infra: containers: cerbos: volumes: - ./infra/cerbos:/policies:roinfraContainers the lanes depend on (databases, brokers, object stores), started and waited on before setup, tasks and services, plus the commands that create and remove each lane's data in them.
Config referenceinfra.containersDocker containers run without a Compose file, keyed by name and reached as infra.<name> in expressions.
infra.containers.<name>Docker container run without a Compose file, shared by every lane or one per lane. Processes reach it through ${{ infra.<name>.ports.<port> }}.
infra.containers.<name>.volumesMounts as source:destination[:mode]. ./relative and /absolute sources are bind mounts; relative ones start at the project file's directory, in the lane's worktree for a per_lane container and in the primary worktree for a shared one. A bare name is a named volume kept per project or per lane.
infra.env
Section titled “infra.env”Type: mapping of names to strings, booleans, numbers or expressions.
Variables for ${VAR} interpolation in the Compose files only; processes do not see them (use global_env for those).
infra: env: ACME_DB_PORT: 15432infraContainers the lanes depend on (databases, brokers, object stores), started and waited on before setup, tasks and services, plus the commands that create and remove each lane's data in them.
Config referenceinfra.envVariables for ${VAR} interpolation in the Compose files only; processes do not see them (use global_env for those).
infra.env.<name>Variables for ${VAR} interpolation in the Compose files only; processes do not see them (use global_env for those).
infra.exclude
Section titled “infra.exclude”Type: list of strings.
Compose services devlanes never starts, such as a local reverse proxy the devlanes proxy replaces.
infra: exclude: - caddyinfraContainers the lanes depend on (databases, brokers, object stores), started and waited on before setup, tasks and services, plus the commands that create and remove each lane's data in them.
Config referenceinfra.excludeCompose services devlanes never starts, such as a local reverse proxy the devlanes proxy replaces.
Config referenceinfra.external
Section titled “infra.external”Type: mapping of names to mappings.
Servers you run yourself on a loopback port, such as pgAdmin, keyed by name. Every lane lists them, the proxy routes their hostnames, and machines connected with devlanes remote connect mirror them while a lane of the project runs. devlanes never starts or checks them. Put personal ones in devlanes.local.yaml.
infra: external: pgadmin: address: 127.0.0.1:5050 hosts: pgadmin.${{ lane.domain }}infraContainers the lanes depend on (databases, brokers, object stores), started and waited on before setup, tasks and services, plus the commands that create and remove each lane's data in them.
Config referenceinfra.externalServers you run yourself on a loopback port, such as pgAdmin, keyed by name. Every lane lists them, the proxy routes their hostnames, and machines connected with devlanes remote connect mirror them while a lane of the project runs. devlanes never starts or checks them. Put personal ones in devlanes.local.yaml.
infra.external.<name>A server you run yourself on a loopback port. Every lane of the project lists it, the proxy routes its hostnames to the port, and machines connected with devlanes remote connect mirror it while a lane of the project runs. The port is the same in every lane.
infra.external.<name>.addressWhere the server listens, 127.0.0.1:<port> or [::1]:<port>. Only loopback addresses work. A port that devlanes or a lane already uses is an error. Required.
infra.external.<name>.hostsHostnames the devlanes HTTPS proxy routes to the port. One entry or a list. An entry is a hostname, or a mapping with host and optional fallback and host_header. Expressions can use lane, project, infra and env. Put the names under ${{ lane.domain }} so each lane gets its own. The first host without a wildcard becomes the unit's URL.
infra.external.<name>
Section titled “infra.external.<name>”Type: mapping.
A server you run yourself on a loopback port. Every lane of the project lists it, the proxy routes its hostnames to the port, and machines connected with devlanes remote connect mirror it while a lane of the project runs. The port is the same in every lane.
infra: external: pgadmin: address: 127.0.0.1:5050 hosts: pgadmin.${{ lane.domain }}infraContainers the lanes depend on (databases, brokers, object stores), started and waited on before setup, tasks and services, plus the commands that create and remove each lane's data in them.
Config referenceinfra.externalServers you run yourself on a loopback port, such as pgAdmin, keyed by name. Every lane lists them, the proxy routes their hostnames, and machines connected with devlanes remote connect mirror them while a lane of the project runs. devlanes never starts or checks them. Put personal ones in devlanes.local.yaml.
infra.external.<name>A server you run yourself on a loopback port. Every lane of the project lists it, the proxy routes its hostnames to the port, and machines connected with devlanes remote connect mirror it while a lane of the project runs. The port is the same in every lane.
infra.external.<name>.addressWhere the server listens, 127.0.0.1:<port> or [::1]:<port>. Only loopback addresses work. A port that devlanes or a lane already uses is an error. Required.
infra.external.<name>.hostsHostnames the devlanes HTTPS proxy routes to the port. One entry or a list. An entry is a hostname, or a mapping with host and optional fallback and host_header. Expressions can use lane, project, infra and env. Put the names under ${{ lane.domain }} so each lane gets its own. The first host without a wildcard becomes the unit's URL.
infra.external.<name>.address
Section titled “infra.external.<name>.address”Type: string.
Where the server listens, 127.0.0.1:<port> or [::1]:<port>. Only loopback addresses work. A port that devlanes or a lane already uses is an error. Required.
infra: external: pgadmin: address: 127.0.0.1:5050infraContainers the lanes depend on (databases, brokers, object stores), started and waited on before setup, tasks and services, plus the commands that create and remove each lane's data in them.
Config referenceinfra.externalServers you run yourself on a loopback port, such as pgAdmin, keyed by name. Every lane lists them, the proxy routes their hostnames, and machines connected with devlanes remote connect mirror them while a lane of the project runs. devlanes never starts or checks them. Put personal ones in devlanes.local.yaml.
infra.external.<name>A server you run yourself on a loopback port. Every lane of the project lists it, the proxy routes its hostnames to the port, and machines connected with devlanes remote connect mirror it while a lane of the project runs. The port is the same in every lane.
infra.external.<name>.addressWhere the server listens, 127.0.0.1:<port> or [::1]:<port>. Only loopback addresses work. A port that devlanes or a lane already uses is an error. Required.
infra.external.<name>.hidden
Section titled “infra.external.<name>.hidden”Type: boolean.
Keep the entry away from machines connected with devlanes remote connect. They never see, mirror or reach it. This machine still routes its hostnames. Defaults to false.
infra: external: pgadmin: hidden: falseinfraContainers the lanes depend on (databases, brokers, object stores), started and waited on before setup, tasks and services, plus the commands that create and remove each lane's data in them.
Config referenceinfra.externalServers you run yourself on a loopback port, such as pgAdmin, keyed by name. Every lane lists them, the proxy routes their hostnames, and machines connected with devlanes remote connect mirror them while a lane of the project runs. devlanes never starts or checks them. Put personal ones in devlanes.local.yaml.
infra.external.<name>A server you run yourself on a loopback port. Every lane of the project lists it, the proxy routes its hostnames to the port, and machines connected with devlanes remote connect mirror it while a lane of the project runs. The port is the same in every lane.
infra.external.<name>.hiddenKeep the entry away from machines connected with devlanes remote connect. They never see, mirror or reach it. This machine still routes its hostnames. Defaults to false.
infra.external.<name>.hosts
Section titled “infra.external.<name>.hosts”Type: string, mapping or an expression, or a list of these.
Hostnames the devlanes HTTPS proxy routes to the port. One entry or a list. An entry is a hostname, or a mapping with host and optional fallback and host_header. Expressions can use lane, project, infra and env. Put the names under ${{ lane.domain }} so each lane gets its own. The first host without a wildcard becomes the unit’s URL.
infra: external: pgadmin: hosts: pgadmin.${{ lane.domain }}infraContainers the lanes depend on (databases, brokers, object stores), started and waited on before setup, tasks and services, plus the commands that create and remove each lane's data in them.
Config referenceinfra.externalServers you run yourself on a loopback port, such as pgAdmin, keyed by name. Every lane lists them, the proxy routes their hostnames, and machines connected with devlanes remote connect mirror them while a lane of the project runs. devlanes never starts or checks them. Put personal ones in devlanes.local.yaml.
infra.external.<name>A server you run yourself on a loopback port. Every lane of the project lists it, the proxy routes its hostnames to the port, and machines connected with devlanes remote connect mirror it while a lane of the project runs. The port is the same in every lane.
infra.external.<name>.hostsHostnames the devlanes HTTPS proxy routes to the port. One entry or a list. An entry is a hostname, or a mapping with host and optional fallback and host_header. Expressions can use lane, project, infra and env. Put the names under ${{ lane.domain }} so each lane gets its own. The first host without a wildcard becomes the unit's URL.
infra.external.<name>.hosts[].fallback
Section titled “infra.external.<name>.hosts[].fallback”Type: boolean or an expression.
Make this route a catch-all: it is used only when no other route, exact or wildcard, matches the requested hostname. Defaults to false.
infra: external: pgadmin: hosts: - host: pgadmin.${{ lane.domain }} fallback: trueinfraContainers the lanes depend on (databases, brokers, object stores), started and waited on before setup, tasks and services, plus the commands that create and remove each lane's data in them.
Config referenceinfra.externalServers you run yourself on a loopback port, such as pgAdmin, keyed by name. Every lane lists them, the proxy routes their hostnames, and machines connected with devlanes remote connect mirror them while a lane of the project runs. devlanes never starts or checks them. Put personal ones in devlanes.local.yaml.
infra.external.<name>A server you run yourself on a loopback port. Every lane of the project lists it, the proxy routes its hostnames to the port, and machines connected with devlanes remote connect mirror it while a lane of the project runs. The port is the same in every lane.
infra.external.<name>.hostsHostnames the devlanes HTTPS proxy routes to the port. One entry or a list. An entry is a hostname, or a mapping with host and optional fallback and host_header. Expressions can use lane, project, infra and env. Put the names under ${{ lane.domain }} so each lane gets its own. The first host without a wildcard becomes the unit's URL.
infra.external.<name>.hosts[].hostHostname to route, evaluated for each lane. A leading *. makes a wildcard that matches any depth below it but not the name itself. Quote it in YAML. Labels hold letters, digits and inner hyphens. Case and a trailing dot are ignored.
infra.external.<name>.hosts[].fallbackMake this route a catch-all: it is used only when no other route, exact or wildcard, matches the requested hostname. Defaults to false.
Config referenceinfra.external.<name>.hosts[].host
Section titled “infra.external.<name>.hosts[].host”Type: string or an expression. Required.
Hostname to route, evaluated for each lane. A leading *. makes a wildcard that matches any depth below it but not the name itself. Quote it in YAML. Labels hold letters, digits and inner hyphens. Case and a trailing dot are ignored.
infra: external: pgadmin: hosts: - host: pgadmin.${{ lane.domain }}infraContainers the lanes depend on (databases, brokers, object stores), started and waited on before setup, tasks and services, plus the commands that create and remove each lane's data in them.
Config referenceinfra.externalServers you run yourself on a loopback port, such as pgAdmin, keyed by name. Every lane lists them, the proxy routes their hostnames, and machines connected with devlanes remote connect mirror them while a lane of the project runs. devlanes never starts or checks them. Put personal ones in devlanes.local.yaml.
infra.external.<name>A server you run yourself on a loopback port. Every lane of the project lists it, the proxy routes its hostnames to the port, and machines connected with devlanes remote connect mirror it while a lane of the project runs. The port is the same in every lane.
infra.external.<name>.hostsHostnames the devlanes HTTPS proxy routes to the port. One entry or a list. An entry is a hostname, or a mapping with host and optional fallback and host_header. Expressions can use lane, project, infra and env. Put the names under ${{ lane.domain }} so each lane gets its own. The first host without a wildcard becomes the unit's URL.
infra.external.<name>.hosts[].hostHostname to route, evaluated for each lane. A leading *. makes a wildcard that matches any depth below it but not the name itself. Quote it in YAML. Labels hold letters, digits and inner hyphens. Case and a trailing dot are ignored.
infra.external.<name>.hosts[].host_header
Section titled “infra.external.<name>.hosts[].host_header”Type: string.
Host header the server receives. Defaults to preserve, the hostname the browser asked for. upstream sends the address devlanes connects to, such as 127.0.0.1:5050, for servers that only accept their own address.
Takes the same values as services.<name>.hosts[].host_header.
infra: external: pgadmin: hosts: - host: pgadmin.${{ lane.domain }} host_header: preserveinfraContainers the lanes depend on (databases, brokers, object stores), started and waited on before setup, tasks and services, plus the commands that create and remove each lane's data in them.
Config referenceinfra.externalServers you run yourself on a loopback port, such as pgAdmin, keyed by name. Every lane lists them, the proxy routes their hostnames, and machines connected with devlanes remote connect mirror them while a lane of the project runs. devlanes never starts or checks them. Put personal ones in devlanes.local.yaml.
infra.external.<name>A server you run yourself on a loopback port. Every lane of the project lists it, the proxy routes its hostnames to the port, and machines connected with devlanes remote connect mirror it while a lane of the project runs. The port is the same in every lane.
infra.external.<name>.hostsHostnames the devlanes HTTPS proxy routes to the port. One entry or a list. An entry is a hostname, or a mapping with host and optional fallback and host_header. Expressions can use lane, project, infra and env. Put the names under ${{ lane.domain }} so each lane gets its own. The first host without a wildcard becomes the unit's URL.
infra.external.<name>.hosts[].hostHostname to route, evaluated for each lane. A leading *. makes a wildcard that matches any depth below it but not the name itself. Quote it in YAML. Labels hold letters, digits and inner hyphens. Case and a trailing dot are ignored.
infra.external.<name>.hosts[].host_headerHost header the server receives. Defaults to preserve, the hostname the browser asked for. upstream sends the address devlanes connects to, such as 127.0.0.1:5050, for servers that only accept their own address.
infra.hidden
Section titled “infra.hidden”Type: list of strings.
Containers that machines connected with devlanes remote connect never see, mirror or reach.
infra: hidden: - postgresinfraContainers the lanes depend on (databases, brokers, object stores), started and waited on before setup, tasks and services, plus the commands that create and remove each lane's data in them.
Config referenceinfra.hiddenContainers that machines connected with devlanes remote connect never see, mirror or reach.
infra.hosts
Section titled “infra.hosts”Type: mapping of names.
HTTPS hostnames for containers, keyed by Compose service or plain container name, so a browser can open a container’s web port: a MinIO console or presigned S3 URLs, Mailpit, a mock OIDC provider. A hostname routes to the container’s first published port unless its route sets port; each key takes one hostname or route, or a list.
infra: hosts: s3mock: s3.${{ lane.domain }}infraContainers the lanes depend on (databases, brokers, object stores), started and waited on before setup, tasks and services, plus the commands that create and remove each lane's data in them.
Config referenceinfra.hostsHTTPS hostnames for containers, keyed by Compose service or plain container name, so a browser can open a container's web port: a MinIO console or presigned S3 URLs, Mailpit, a mock OIDC provider. A hostname routes to the container's first published port unless its route sets port; each key takes one hostname or route, or a list.
infra.hosts.<name>HTTPS hostnames the devlanes proxy routes to this unit, so a browser reaches it at https://<host>: one hostname or route mapping, or a list of them.
infra.hosts.<name>
Section titled “infra.hosts.<name>”Type: string, mapping or an expression, or a list of these.
HTTPS hostnames the devlanes proxy routes to this unit, so a browser reaches it at https://<host>: one hostname or route mapping, or a list of them.
Takes the same keys as services.<name>.hosts.
infra: hosts: s3mock: api.${{ lane.domain }}infraContainers the lanes depend on (databases, brokers, object stores), started and waited on before setup, tasks and services, plus the commands that create and remove each lane's data in them.
Config referenceinfra.hostsHTTPS hostnames for containers, keyed by Compose service or plain container name, so a browser can open a container's web port: a MinIO console or presigned S3 URLs, Mailpit, a mock OIDC provider. A hostname routes to the container's first published port unless its route sets port; each key takes one hostname or route, or a list.
infra.hosts.<name>HTTPS hostnames the devlanes proxy routes to this unit, so a browser reaches it at https://<host>: one hostname or route mapping, or a list of them.
infra.per_lane
Section titled “infra.per_lane”Type: list of strings.
Compose services run once per lane instead of shared, each in its own Compose project with ports from the lane’s block and its own named volumes, removed by devlanes lane clean. Needs Compose 2.24.4 or newer.
infra: per_lane: - mailpitinfraContainers the lanes depend on (databases, brokers, object stores), started and waited on before setup, tasks and services, plus the commands that create and remove each lane's data in them.
Config referenceinfra.per_laneCompose services run once per lane instead of shared, each in its own Compose project with ports from the lane's block and its own named volumes, removed by devlanes lane clean. Needs Compose 2.24.4 or newer.
infra.profiles
Section titled “infra.profiles”Type: list of strings.
Compose profiles to enable when resolving and starting the Compose services.
infra: profiles: - developmentinfraContainers the lanes depend on (databases, brokers, object stores), started and waited on before setup, tasks and services, plus the commands that create and remove each lane's data in them.
Config referenceinfra.profilesCompose profiles to enable when resolving and starting the Compose services.
Config referenceinfra.project_name
Section titled “infra.project_name”Type: string or an expression.
Name of the shared Compose project, fixed so docker compose -p <name> reaches the same containers outside devlanes. Defaults to the name Compose picks itself.
infra: project_name: acmeinfraContainers the lanes depend on (databases, brokers, object stores), started and waited on before setup, tasks and services, plus the commands that create and remove each lane's data in them.
Config referenceinfra.project_nameName of the shared Compose project, fixed so docker compose -p <name> reaches the same containers outside devlanes. Defaults to the name Compose picks itself.
infra.setup
Section titled “infra.setup”Type: mapping of names.
Named commands that prepare each lane’s data, such as creating its database in a shared Postgres. They run once per lane after the containers are ready, all at the same time, and are recorded as done so later starts skip them; a failure stops the start unless the entry sets ignore_errors.
infra: setup: database: docker compose exec -T postgres createdb acme_${{ lane.name }}infraContainers the lanes depend on (databases, brokers, object stores), started and waited on before setup, tasks and services, plus the commands that create and remove each lane's data in them.
Config referenceinfra.setupNamed commands that prepare each lane's data, such as creating its database in a shared Postgres. They run once per lane after the containers are ready, all at the same time, and are recorded as done so later starts skip them; a failure stops the start unless the entry sets ignore_errors.
infra.setup.<name>Command that prepares (setup) or removes (teardown) a lane's data: a command string or list, or a mapping with run and options such as container, ignore_errors and timeout. Task steps can run it as infra.setup.<name> or infra.teardown.<name>.
infra.setup.<name>
Section titled “infra.setup.<name>”Type: mapping, string, list of strings or an expression.
Command that prepares (setup) or removes (teardown) a lane’s data: a command string or list, or a mapping with run and options such as container, ignore_errors and timeout. Task steps can run it as infra.setup.<name> or infra.teardown.<name>.
infra: setup: database: docker compose exec -T postgres createdb acme_${{ lane.name }}infraContainers the lanes depend on (databases, brokers, object stores), started and waited on before setup, tasks and services, plus the commands that create and remove each lane's data in them.
Config referenceinfra.setupNamed commands that prepare each lane's data, such as creating its database in a shared Postgres. They run once per lane after the containers are ready, all at the same time, and are recorded as done so later starts skip them; a failure stops the start unless the entry sets ignore_errors.
infra.setup.<name>Command that prepares (setup) or removes (teardown) a lane's data: a command string or list, or a mapping with run and options such as container, ignore_errors and timeout. Task steps can run it as infra.setup.<name> or infra.teardown.<name>.
infra.setup.<name>.container
Section titled “infra.setup.<name>.container”Type: string.
Run this setup entry again whenever the named container has restarted since it last ran, for data that lives in the container and may be gone, such as a RabbitMQ vhost.
infra: setup: database: container: rabbitmqinfraContainers the lanes depend on (databases, brokers, object stores), started and waited on before setup, tasks and services, plus the commands that create and remove each lane's data in them.
Config referenceinfra.setupNamed commands that prepare each lane's data, such as creating its database in a shared Postgres. They run once per lane after the containers are ready, all at the same time, and are recorded as done so later starts skip them; a failure stops the start unless the entry sets ignore_errors.
infra.setup.<name>Command that prepares (setup) or removes (teardown) a lane's data: a command string or list, or a mapping with run and options such as container, ignore_errors and timeout. Task steps can run it as infra.setup.<name> or infra.teardown.<name>.
infra.setup.<name>.containerRun this setup entry again whenever the named container has restarted since it last ran, for data that lives in the container and may be gone, such as a RabbitMQ vhost.
Config referenceinfra.setup.<name>.cwd
Section titled “infra.setup.<name>.cwd”Type: string or an expression.
Working directory, relative to the project file’s directory in the lane’s worktree; defaults to that directory.
infra: setup: database: cwd: infrainfraContainers the lanes depend on (databases, brokers, object stores), started and waited on before setup, tasks and services, plus the commands that create and remove each lane's data in them.
Config referenceinfra.setupNamed commands that prepare each lane's data, such as creating its database in a shared Postgres. They run once per lane after the containers are ready, all at the same time, and are recorded as done so later starts skip them; a failure stops the start unless the entry sets ignore_errors.
infra.setup.<name>Command that prepares (setup) or removes (teardown) a lane's data: a command string or list, or a mapping with run and options such as container, ignore_errors and timeout. Task steps can run it as infra.setup.<name> or infra.teardown.<name>.
infra.setup.<name>.cwdWorking directory, relative to the project file's directory in the lane's worktree; defaults to that directory.
Config referenceinfra.setup.<name>.env
Section titled “infra.setup.<name>.env”Type: mapping of names to strings, booleans, numbers or expressions.
Variables for this command only.
infra: setup: database: env: AWS_DEFAULT_REGION: us-east-1infraContainers the lanes depend on (databases, brokers, object stores), started and waited on before setup, tasks and services, plus the commands that create and remove each lane's data in them.
Config referenceinfra.setupNamed commands that prepare each lane's data, such as creating its database in a shared Postgres. They run once per lane after the containers are ready, all at the same time, and are recorded as done so later starts skip them; a failure stops the start unless the entry sets ignore_errors.
infra.setup.<name>Command that prepares (setup) or removes (teardown) a lane's data: a command string or list, or a mapping with run and options such as container, ignore_errors and timeout. Task steps can run it as infra.setup.<name> or infra.teardown.<name>.
infra.setup.<name>.ignore_errors
Section titled “infra.setup.<name>.ignore_errors”Type: boolean or an expression.
Count a failed or timed-out command as done instead of failing the start, for commands whose “already exists” error is fine. Defaults to false.
infra: setup: database: ignore_errors: trueinfraContainers the lanes depend on (databases, brokers, object stores), started and waited on before setup, tasks and services, plus the commands that create and remove each lane's data in them.
Config referenceinfra.setupNamed commands that prepare each lane's data, such as creating its database in a shared Postgres. They run once per lane after the containers are ready, all at the same time, and are recorded as done so later starts skip them; a failure stops the start unless the entry sets ignore_errors.
infra.setup.<name>Command that prepares (setup) or removes (teardown) a lane's data: a command string or list, or a mapping with run and options such as container, ignore_errors and timeout. Task steps can run it as infra.setup.<name> or infra.teardown.<name>.
infra.setup.<name>.ignore_errorsCount a failed or timed-out command as done instead of failing the start, for commands whose "already exists" error is fine. Defaults to false.
Config referenceinfra.setup.<name>.run
Section titled “infra.setup.<name>.run”Type: string, list of strings or an expression.
Command to run: a string runs through /bin/sh -c, a list runs the program directly. Write the command you mean, such as docker compose exec -T postgres ...; devlanes runs it as written. Required. In a list, an item that is one ${{ }} expression giving a number or true/false becomes its text, such as --port followed by ${{ self.port }}.
infra: setup: database: run: pnpm devinfraContainers the lanes depend on (databases, brokers, object stores), started and waited on before setup, tasks and services, plus the commands that create and remove each lane's data in them.
Config referenceinfra.setupNamed commands that prepare each lane's data, such as creating its database in a shared Postgres. They run once per lane after the containers are ready, all at the same time, and are recorded as done so later starts skip them; a failure stops the start unless the entry sets ignore_errors.
infra.setup.<name>Command that prepares (setup) or removes (teardown) a lane's data: a command string or list, or a mapping with run and options such as container, ignore_errors and timeout. Task steps can run it as infra.setup.<name> or infra.teardown.<name>.
infra.setup.<name>.runCommand to run: a string runs through /bin/sh -c, a list runs the program directly. Write the command you mean, such as docker compose exec -T postgres ...; devlanes runs it as written. Required. In a list, an item that is one ${{ }} expression giving a number or true/false becomes its text, such as --port followed by ${{ self.port }}.
infra.setup.<name>.timeout
Section titled “infra.setup.<name>.timeout”Type: duration or an expression.
Longest the command may run. When it runs out, the command is stopped (SIGTERM, then SIGKILL after 10 seconds) and counts as failed, so a setup entry fails the start unless ignore_errors is set. No limit by default.
infra: setup: database: timeout: 15sinfraContainers the lanes depend on (databases, brokers, object stores), started and waited on before setup, tasks and services, plus the commands that create and remove each lane's data in them.
Config referenceinfra.setupNamed commands that prepare each lane's data, such as creating its database in a shared Postgres. They run once per lane after the containers are ready, all at the same time, and are recorded as done so later starts skip them; a failure stops the start unless the entry sets ignore_errors.
infra.setup.<name>Command that prepares (setup) or removes (teardown) a lane's data: a command string or list, or a mapping with run and options such as container, ignore_errors and timeout. Task steps can run it as infra.setup.<name> or infra.teardown.<name>.
infra.setup.<name>.timeoutLongest the command may run. When it runs out, the command is stopped (SIGTERM, then SIGKILL after 10 seconds) and counts as failed, so a setup entry fails the start unless ignore_errors is set. No limit by default.
infra.teardown
Section titled “infra.teardown”Type: mapping of names.
Named commands that remove a lane’s data when the lane is cleaned (devlanes lane clean), one after another; never on stop. A failure is reported and the cleanup goes on.
infra: teardown: database: docker compose exec -T postgres dropdb --if-exists acme_${{ lane.name }}infraContainers the lanes depend on (databases, brokers, object stores), started and waited on before setup, tasks and services, plus the commands that create and remove each lane's data in them.
Config referenceinfra.teardownNamed commands that remove a lane's data when the lane is cleaned (devlanes lane clean), one after another; never on stop. A failure is reported and the cleanup goes on.
infra.teardown.<name>Command that prepares (setup) or removes (teardown) a lane's data: a command string or list, or a mapping with run and options such as container, ignore_errors and timeout. Task steps can run it as infra.setup.<name> or infra.teardown.<name>.
infra.teardown.<name>
Section titled “infra.teardown.<name>”Type: mapping, string, list of strings or an expression.
Command that prepares (setup) or removes (teardown) a lane’s data: a command string or list, or a mapping with run and options such as container, ignore_errors and timeout. Task steps can run it as infra.setup.<name> or infra.teardown.<name>.
Takes the same keys as infra.setup.<name>.
infra: teardown: database: docker compose exec -T postgres createdb acme_${{ lane.name }}infraContainers the lanes depend on (databases, brokers, object stores), started and waited on before setup, tasks and services, plus the commands that create and remove each lane's data in them.
Config referenceinfra.teardownNamed commands that remove a lane's data when the lane is cleaned (devlanes lane clean), one after another; never on stop. A failure is reported and the cleanup goes on.
infra.teardown.<name>Command that prepares (setup) or removes (teardown) a lane's data: a command string or list, or a mapping with run and options such as container, ignore_errors and timeout. Task steps can run it as infra.setup.<name> or infra.teardown.<name>.