Skip to content

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

Keep personal changes out of Git

Use this guide when you want the project to run a little differently on your machine, such as one service off or a debug log level, without changing the project file the team shares.

::example{slug="workflows-dev-and-prod"}

The local file is devlanes.local.yaml, next to devlanes.yaml. It takes the same keys and holds only what you change, merged over the project file:

devlanes.local.yaml
services:
web:
autostart: false
api:
env:
LOG_LEVEL: debug
scratch:
run_script:
file: apps/scratch/package.json
name: dev
hosts: "scratch.${{ lane.domain }}"

Here a plain start leaves the web service out unless the lane ran it before or you name it, the API gets one more variable and keeps the rest, and a service only you run joins the lane. The local file cannot set project or a file-level extends. Config files and reload has the merge rules.

devlanes does not touch your .gitignore, so add the file yourself:

.gitignore
devlanes*.local.yaml
~/dev/myapp
$ devlanes reload

The reload restarts the services your edit changed. A new worktree has no local file of its own and reads the primary worktree’s, as Files and folders describes.

Create a local file in that worktree. Its lanes read that file instead of the primary worktree’s, and the two are not merged.

Each project file has its own local file, named after it: devlanes.prod.yaml reads devlanes.prod.local.yaml. Run dev servers and a production build side by side sets up such a pair.