1
Start the dev server
The commands below use
my-app and npm run dev as stand-ins for your own app’s folder and
start command.push reports how many files it pushed to dev:/data/home/my-app. exec --background prints
the job’s ID and the instabox jobs logs command that follows it.--background keeps the server running after the command returns. With a plain exec, start
the server with nohup ./server >server.log 2>&1 &, and redirect both stdout and stderr.2
Publish the port
https://<port>-<machine id without m_>.<domain>/. For a private
port it prints the link with ?_token= instead.3
Share the link
Send the printed URL. A browser that opens a private link gets a cookie and goes on to the plain
URL, WebSockets included. Scripts send
Authorization: Bearer ibp_... instead. Everyone else
gets 401.4
Rotate or remove the link
port ls shows each published port with its access and URL.A visit wakes a machine that paused itself for being idle. The request waits for the machine to
resume. A machine you paused or stopped stays offline at the same URL until you resume or start
it. After a stop, start your server again.
instabox-port. Where instabox-port is missing,
instabox port setup dev installs it.
Only for you: port-forward
Only for you: port-forward
instabox port-forward dev 8080:3000 makes port 3000 reachable at http://127.0.0.1:8080 on your
computer until Ctrl-C, with no URL at all. It reaches any TCP service.Limits
Limits
A machine has up to 16 published ports. A response header may be up to 24 KiB. A larger one gets
the platform’s
502 page. Requests to a private port without its token never wake the machine.Public and private ports
Public, private, and raw TCP ports in full.
Auto-pause and max-run
When a machine pauses and what wakes it.