How it works
Every machine automatically gets a default proxy at<machine>.boxd.sh. It detects the port your app listens on among 80, 443, 8080, 8000, 3000, 5000 and 5173, and falls back to 8000:
nyc.boxd.sh, such as https://myapp.nyc.boxd.sh and https://api.myapp.nyc.boxd.sh.
DNS records are created automatically when the machine boots. Records have a 60-second TTL.
The HTTPS page covers the default domain itself: getting your first app reachable on it, WebSockets, and the HTTP to HTTPS redirect.
View your proxies
From your laptop, list the proxies of all your machines:Create a subdomain proxy
Each subdomain proxy gets its own domain at<name>.<machine>.boxd.sh:
api.myapp.boxd.sh and forwards HTTPS traffic to port 3001 on your machine.
Inside a machine, the command is proxy new, and it targets the machine you are in:
Remove a proxy
proxy rm.
Change the default port
--vm to target the machine you are in:
--port auto to go back to detecting the listening port.
Non-HTTP services
Proxies route HTTPS only. To expose a database, an SSH daemon, a game server, or any other raw protocol, add a raw port forward instead. See Port forwarding.Custom domains
Bring your own domain instead of<machine>.boxd.sh: point it at one machine, or delegate a wildcard to your whole organization. See Custom domains.