Skip to content

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

profiles in devlanes.yaml

A top-level key of devlanes.yaml.

Type: mapping of names.

Named selections of services for devlanes start --profile <name>. A plain devlanes start brings back what the lane ran before; default is used when there is nothing to bring back, such as after devlanes stop. A profile is a list of names, globs and +tag selectors, or a mapping that can also exclude services, skip infra, add env and remap script names.

devlanes.yaml
profiles:
default:
- +api
- +web
e2e:
include:
- "*"
run_scripts:
dev: start

Type: list of strings or mapping.

Services started by devlanes start --profile <name> (default when no profile is given): a list of names, globs and +tag selectors, or a mapping that can also exclude services, skip infra, add env and remap script names. Several --profile flags start the union.

devlanes.yaml
profiles:
default:
- +api
- +web

Type: mapping of names to strings, booleans, numbers or expressions.

Variables for the services, tasks and infra.setup and infra.teardown commands of a lane while this profile is active, and for devlanes exec and devlanes with when they read neither self nor replica. They sit above each unit’s own env, which cannot override them, so put a variable that some task must not get, such as NODE_ENV: production next to an install task that needs devDependencies, in global_env instead.

devlanes.yaml
profiles:
default:
env:
LOG_LEVEL: warn

Type: list of strings.

Services removed from the include selection, by name, glob or +tag.

devlanes.yaml
profiles:
default:
exclude:
- +desktop
- sms-stub

Type: list of strings.

Services this profile starts: names, globs such as crm-*, and +tag selectors. Globs skip services with autostart: false; names and tags include them.

devlanes.yaml
profiles:
default:
include:
- +api
- +web

Type: boolean or an expression.

Set false to skip containers and infra.setup, for example to run only a frontend against another lane’s backend. A value that reads infra.* then resolves only while its container already runs, as a shared one another lane started does. Otherwise a service or task whose env reads it fails to start, and so does every service and task of the lane when global_env or a profile’s env reads it. With several profiles active, infra is skipped only when all of them set false. Defaults to true.

devlanes.yaml
profiles:
default:
infra: false

Type: mapping of names to strings.

Swap script names for services that use run_script: { dev: start } runs the start script wherever a service’s run_script names dev. The file stays the same, and each name is swapped once, not chained. The whole name is matched, so a Maven or Gradle name such as spring-boot:run -Pdev is swapped only by that exact text.

devlanes.yaml
profiles:
default:
run_scripts:
dev: start