Docs · CLI
Publishing URLs.
Expose any dev server on your workstation to a stable <branch>.<svc>.<user>.remoco.dev URL. Private by default, public on demand. One flag flips it.
Publish (private)
$ remoco expose main.web.wiley # adds cloudflared ingress rule · sets up CF Access app # creates DNS record if missing · restarts the tunnel # live at https://main.web.wiley.remoco.dev (gated by WorkOS SSO)
Publish (public)
$ remoco expose main.web.wiley --access=public # removes the CF Access app # snapshots the current workspace · public URL serves from snapshot # your private preview keeps hot-reloading
List
$ remoco links alias access URL main.web.wiley private https://main.web.wiley.remoco.dev main.tetris.wiley public https://main.tetris.wiley.remoco.dev debug.wiley private https://debug.wiley.remoco.dev
Hide
$ remoco hide main.web.wiley # removes ingress + DNS + Access app
Ephemeral share (trycloudflare)
For one-off sharing without a stable URL, use a quick tunnel:
$ remoco share 3333 # https://random-words.trycloudflare.com → localhost:3333 on your workstation
How it works under the hood
- The CLI appends an ingress rule to
~/.cloudflared/config.yml - Rewrites the
Host:header to the internal.localhostform - Creates DNS via
cloudflared tunnel route dns - For private: creates a CF Access app with a WorkOS SSO policy
- Restarts the tunnel tmux session so cloudflared picks up the new config
v0.2. Publishing moves server-side.
POST /v1/expose applies directly; the workstation CLI becomes a thin client.