Skip to content

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

Choose what a box shares

A connected machine mirrors each service and container that the box’s lanes run, and you can keep some of them on the box or add a server you run there yourself. Environments, secrets and logs stay on the box either way, as Remote mirroring explains.

::example{slug="remote-docker-box"}

Put these lines in the project file on the box, or in the local file next to it when only your box needs them.

Mark the service as hidden with services.<name>.hidden. Machines that connect never see it, and it runs on the box as before.

devlanes.yaml
# devlanes.local.yaml on the box
services:
admin:
hidden: true

A running service keeps the setting it started with, so restart it on the box.

~/dev/myapp on the box
$ devlanes restart admin

List the containers by name under infra.hidden.

devlanes.yaml
infra:
hidden: [postgres]

A server you start on the box yourself is reachable from your machine once the box’s config declares its address and hostname. Your machine mirrors it while a lane of the project runs on the box. Pick a port outside the box’s port range.

devlanes.yaml
# devlanes.local.yaml on the box
infra:
external:
files:
address: 127.0.0.1:8000
hosts: "files.${{ lane.domain }}"

Give a server you run yourself a hostname covers the entry. To declare one and still keep it on the box, set infra.external.<name>.hidden.