profiles in devlanes.yaml
A top-level key of devlanes.yaml.
profiles
Section titled “profiles”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.
profiles: default: - +api - +web e2e: include: - "*" run_scripts: dev: startprofilesNamed 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.
profiles.<name>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.
profiles.<name>.includeServices this profile starts: names, globs such as crm-*, and +tag selectors. Globs skip services with autostart: false; names and tags include them.
profiles.<name>.run_scriptsSwap 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.
profiles.<name>.run_scripts.<name>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.
profiles.<name>
Section titled “profiles.<name>”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.
profiles: default: - +api - +webprofilesNamed 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.
profiles.<name>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.
profiles.<name>.env
Section titled “profiles.<name>.env”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.
profiles: default: env: LOG_LEVEL: warnprofilesNamed 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.
profiles.<name>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.
profiles.<name>.envVariables 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.
profiles.<name>.env.<name>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.
profiles.<name>.exclude
Section titled “profiles.<name>.exclude”Type: list of strings.
Services removed from the include selection, by name, glob or +tag.
profiles: default: exclude: - +desktop - sms-stubprofilesNamed 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.
profiles.<name>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.
profiles.<name>.excludeServices removed from the include selection, by name, glob or +tag.
profiles.<name>.include
Section titled “profiles.<name>.include”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.
profiles: default: include: - +api - +webprofilesNamed 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.
profiles.<name>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.
profiles.<name>.includeServices this profile starts: names, globs such as crm-*, and +tag selectors. Globs skip services with autostart: false; names and tags include them.
profiles.<name>.infra
Section titled “profiles.<name>.infra”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.
profiles: default: infra: falseprofilesNamed 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.
profiles.<name>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.
profiles.<name>.infraSet 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.
profiles.<name>.run_scripts
Section titled “profiles.<name>.run_scripts”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.
profiles: default: run_scripts: dev: startprofilesNamed 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.
profiles.<name>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.
profiles.<name>.run_scriptsSwap 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.
profiles.<name>.run_scripts.<name>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.