Skip to content

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

Many datastores with a namespace per lane

A TypeScript server over Postgres, Redis, ClickHouse, RabbitMQ and an S3 store that every lane shares, with its own database, Redis index, ClickHouse database, vhost and bucket in each lane. Each lane also gets its own Mailpit, and the web consoles are on HTTPS hostnames.

  • devlanes, with devlanes setup run once
  • Docker with Compose 2.24.4 or newer
  • Node 22 or later
Terminal window
cd infra-multi-database
devlanes start

devlanes start --no-ui prints the start as text:

example-multi-database@0 (main): 1/1 ready
ready api http://127.0.0.1:20430 https://example-multi-database.localhost

The first start pulls the images, about 2.5 GB in docker image ls. Open https://example-multi-database.localhost. The page says This is lane 0 of example-multi-database. and shows one card per store with this lane’s namespace, a health line and a Write and read button that writes to the store and prints what it read back.

StoreContainerLane 0Lane 1Reason
Postgresshareddatabase app_mainapp_lane1A database keeps tables, migrations and connections apart, and one server is enough for every branch. Use a per-lane Postgres when branches need different versions or destructive migrations (infra-postgres-per-lane).
Redissharedindex 01An index costs nothing and FLUSHDB clears one lane. Redis has 16 by default, so lanes 16 and up would need databases raised.
ClickHouseshareddatabase app_mainapp_lane1The server takes a few hundred MB of memory, too much to run once per lane.
RabbitMQsharedvhost app_mainapp_lane1A vhost has its own queues, exchanges and permissions.
S3 (RustFS)sharedbucket app-mainapp-lane1One bucket per lane, with a dash because bucket names allow no underscore.
Mailpitper laneCompose project example-multi-database-lane0example-multi-database-lane1Mailpit has nothing to namespace: every message lands in one inbox. A container per lane gives each lane its own inbox, and lane clean removes it.

MinIO no longer publishes images (its Docker Hub repositories were removed in September 2026), so the S3 store is RustFS, which speaks the same S3 API and has a web console. The rc service in docker-compose.yml is its command line, kept out of docker compose up by a Compose profile.

  1. The shared containers start in the Compose project example-multi-database (infra.project_name), then this lane’s Mailpit in example-multi-database-lane0. devlanes waits for every healthcheck.
  2. The infra.setup entries run at the same time, once per lane, and are recorded as done. Each runs inside its container (docker compose exec -T or docker compose run --rm), so the host needs no psql, redis-cli, clickhouse-client or S3 CLI:
    • postgres pipes SELECT 'CREATE DATABASE ...' WHERE NOT EXISTS (...) \gexec into psql;
    • redis sets lane:owner in the lane’s index, which the Redis card shows;
    • clickhouse runs CREATE DATABASE IF NOT EXISTS;
    • rabbitmq waits for the node, adds the vhost and grants the app user on it;
    • s3 runs rc bucket create --ignore-existing in a throwaway rc container.
  3. The install task (when: lane.create) runs npm install on the lane’s first start.
  4. api starts with npm run dev (tsx watch src/index.ts) and the URLs from global_env (DATABASE_URL, REDIS_URL, CLICKHOUSE_URL, AMQP_URL, S3_URL, SMTP_URL), and is ready once /healthz answers.

Every entry can run again without harm, as devlanes run infra.setup.postgres shows.

All on the lane’s domain:

HostnameContainer portLogin
https://rustfs.example-multi-database.localhost/rustfs/console/9001rustfsadmin / rustfsadmin
https://rabbitmq.example-multi-database.localhost15672app / app
https://clickhouse.example-multi-database.localhost/play8123app / app
https://mail.example-multi-database.localhost8025none

The shared consoles show every lane’s databases, vhosts and buckets; Mailpit shows only the lane’s own mail. Postgres and Redis have no console and are in infra.hidden, so a machine connected with devlanes remote connect does not mirror their raw ports; remove a name there to reach a box’s database from your own client. Run a query in them like this:

Terminal window
docker compose -p example-multi-database exec -T postgres psql -U postgres app_main -c 'SELECT count(*) FROM notes'

Outside devlanes, always pass -p example-multi-database: a plain docker compose in this folder uses a project named after the folder.

devlanes infra status lists both Compose projects with their health and host ports (excerpt):

infra for example-multi-database@0
shared:
project: example-multi-database
services: clickhouse, postgres, rabbitmq, redis, rustfs
...
lane:
project: example-multi-database-lane0
services: mailpit
  • Start a second lane: git worktree add ../examples-checkout -b feat/checkout, then cd ../examples-checkout/infra-multi-database && devlanes start. In this folder, devlanes lane new --name example-multi-database-review --start gives lane 1 without a worktree, and is what the output below comes from. https://example-multi-database1.localhost shows This is lane 1 of example-multi-database. using the same containers with its own namespaces, and devlanes env show api --lane example-multi-database-review lists its URLs (excerpt):

    AMQP_URL=amqp://app:app@127.0.0.1:55408/app_lane1
    CLICKHOUSE_URL=http://app:app@127.0.0.1:55410/app_lane1
    DATABASE_URL=postgres://postgres:postgres@127.0.0.1:55404/app_lane1
    REDIS_URL=redis://127.0.0.1:55413/1
    S3_URL=http://rustfsadmin:rustfsadmin@127.0.0.1:55418/app-lane1
    SMTP_URL=smtp://127.0.0.1:20591

    The ports of the shared stores match lane 0’s; only the SMTP port belongs to the lane’s own Mailpit.

  • Press Write and read on the Mailpit card of lane 1. The mail shows up at https://mail.example-multi-database1.localhost and not at https://mail.example-multi-database.localhost.

  • Restart RabbitMQ with docker compose -p example-multi-database restart rabbitmq, then run devlanes restart. Docker gives the restarted container a new host port, which the lane restart reads back. Because the rabbitmq entry sets container: rabbitmq, the restart also runs it again, and devlanes logs setup.rabbitmq shows another Adding vhost "app_main" ... line; the other entries stay done. A plain devlanes start runs the entry again too, but in devlanes 0.11.3 it leaves api and the console route on the old port, so the RabbitMQ card shows connect ECONNREFUSED until the restart.

  • Clean the second lane with devlanes lane clean example-multi-database-review --yes (devlanes lane clean 1 --yes for the worktree’s lane). It prints cleaned example-multi-database@1: stopped 1 unit, teardown postgres, redis, clickhouse, rabbitmq, s3. app_lane1, index 1, the vhost and the app-lane1 bucket with its objects are gone, lane 1’s Mailpit container is removed, and lane 0’s data is untouched.

  • Remove everything this example created: devlanes lane clean 0 --yes, then devlanes infra down to stop the shared containers, then docker compose -p example-multi-database down -v to delete them with their volumes. The next devlanes start creates everything again.

  • devlanes.yaml: the per-lane names, setup and teardown for each store, console hostnames, the URLs in global_env, the install task and the api service.
  • docker-compose.yml: the containers with pinned images, loopback ports and healthchecks, plus the rc S3 command line under a profile.
  • src/stores/: one module per store with its namespace, health check and write-then-read.
  • src/routes/: the dashboard at /, the POST /stores/<store>/try action of each card and GET /api/stores.