Skip to content

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

Migrate from another process manager

Use this guide when mprocs, a Procfile, process-compose, pm2, tmuxinator, concurrently or Docker Compose runs your dev processes today. A coding agent with the devlanes skill does the migration; paste this into it from the repository.

Install the devlanes skill:
npx skills add devlanes-run/devlanes --skill devlanes
Then install devlanes on this machine, set up everything it needs,
and help me port this project to devlanes from whatever runs it today.

::example{slug="workflows-mprocs-migration"}

The agent keeps the old files, so people who do not use devlanes keep their setup. Its project file follows these rules:

  • A process that keeps running becomes a service with a ready check.
  • A command that ends by itself, such as an install or a migration, becomes a task.
  • A container stays in its Compose file, which the project file runs under infra.
  • A fixed port becomes the port devlanes gives the service in each lane.
Procfile.dev
web: bin/rails server -p $PORT
devlanes.yaml
services:
web:
run: bin/rails server -p $PORT -b 127.0.0.1
hosts: "${{ lane.domain }}"
ready:
http:
path: /up

If Caddy, nginx or Traefik served the project until now, the devlanes proxy takes its place, and the old one has to let go of ports 443 and 80. While its container runs, lane URLs carry port 8443, and an app that builds its URLs without a port gets them wrong. Remove the container, then restart the daemon so its proxy takes the ports:

~/dev/myapp
$ docker compose rm -sf caddy
$ devlanes daemon restart

Choose the proxy’s ports shows how to check which ports the proxy has.

The agent lists the ones your setup had:

If you would rather write the file yourself

Section titled “If you would rather write the file yourself”

Add devlanes to a project goes through it step by step.