devmachine

Concepts

Publishing

Two ways to reach a port running on a machine: expose puts it on the internet, tunnel reaches it only from your computer. Neither is the default — you pick based on who should reach it.

devmachine expose add acme 3000 --host app.example.com
devmachine tunnel acme 5432

Which one to use

AnyoneOnly you
HTTPexposetunnel
Anything elsenothingtunnel

expose only works for HTTP, and only puts up an HTTPS address — nothing else goes on the internet. tunnel works for anything, HTTP or not, and never touches DNS.

Speaking HTTP doesn’t mean “safe to publish”. A database viewer, a captured-mail inbox, a queue dashboard that can drain a queue: all three speak HTTP, none has its own login, and none should go through expose. Use tunnel for those — it looks at the thing from your computer, without ever making it public.

Where a published app is recorded

In config.yml, on the workspace, under routes:. expose add records it there and puts it on Caddy at once, in seconds; expose rm takes it off the same way. sync writes the same file, so it is also what brings the site back after a rebuild, or publishes it when the machine was out of reach. See why a published app lives in the configuration.

A machine the internet cannot reach

A port on a machine with no public address — a VM on your desk, a box behind NAT — is published by another machine that has Caddy: expose add acme 8080 --host app.example.com --via edge. Visitors need nothing; only the two machines have to reach each other, over the address the workspace’s machine has in hosts. See publishing through another machine.

Why expose asks first

expose add tells you, before it does anything, that the port becomes reachable by anybody who learns the hostname. In a script, pass --publish to confirm that on purpose — --yes alone never does. The same rule protects dns add.