The words the devlanes docs use most, in alphabetical order, each with the page that explains it.
| Term | Meaning | Explained in |
|---|---|---|
| Box | A machine whose lanes show up on another. | Remote mirroring |
| CA | The certificate authority devlanes creates on your machine to sign the certificates of its hostnames. | Hostnames and HTTPS |
| Container | Something under infra, such as a Compose service. | A database for each lane |
| Daemon | The background process that runs the lanes. | The daemon |
| Data folder | A folder of each lane outside its worktree, read as ${{ lane.data_path }}. | Files and folders |
| Drift | A difference between what a lane runs and what its project file now says, which devlanes reload applies. | Config files and reload |
| Expression | A ${{ ... }} value in the project file, evaluated for each lane. | Expressions |
| Frozen, thaw | A lane nobody uses is suspended, and runs again on its next request, connection or command. | Throttling and freezing |
| Hostname | A name the proxy serves over HTTPS, such as api.myapp1.localhost. | Hostnames and HTTPS |
| Lane | One worktree’s place to run the project, with ports, hostnames and data of its own. | Lanes and projects |
| Lane 0 | The lane of the worktree that has the project’s primary branch, such as main, checked out. | Lanes and projects |
| Lane domain | The domain a lane’s hostnames end in: myapp.localhost in lane 0, myapp1.localhost in lane 1. | Hostnames and HTTPS |
| Lane name | main for lane 0 and lane<N> for lane N. | Lanes and projects |
| Local file | devlanes.local.yaml: one developer’s changes to the project file, kept out of Git. | Keep personal changes out of Git |
| Pairing | Proving to a box, with a one-time code from devlanes daemon pair, that your machine may connect to it. | Security |
| Port block | The range of consecutive ports each lane gets. | Ports |
| Preset | A service setting, such as preset: vite, that passes a framework its port and other per-lane settings. | Services that find each other |
| Profile | A named set of services, and their settings, that a start can select. | Share settings and choose which services start |
| Project | What one devlanes.yaml describes. | Lanes and projects |
| Project file | devlanes.yaml. | A service, a port and a hostname |
| Proxy | The part of the daemon that serves every hostname over HTTPS and passes each request to its lane. | Hostnames and HTTPS |
| Ready check | ready: how devlanes decides that a service works. | Wait until a service is ready |
| Reload | devlanes reload, which applies changes to the project file to the running lane. | Config files and reload |
| Service | A long-running process of a lane. | A service, a port and a hostname |
| Setup | infra.setup entries: commands run once per lane after its containers are ready, such as creating its database. | A database for each lane |
| Shared container | A container every lane of the project uses, such as one Postgres with a database per lane. | Share one database server between lanes |
| Task | A one-off command of a lane, such as an install or a migration. | Run installs, migrations and seeds |
| Unit | A service, task or command that a lane runs. | Lane and unit references |
| User config | ~/.devlanes/config.yaml. | Files and folders |
| Worktree | A Git worktree. | Every worktree gets a lane |