Getting startedQuickstart
What the deploy did
From a folder with two files, ferry up made a web service with a URL.
Pack. ferry up packs the current folder and sends the archive.
1 / 7
Find each step in the log
Packing /home/you/ferry/examples/node-hello …
Packed 2 file(s), 576 B
Created web service 'node-hello' (srv-8593a88388f349feade2)
Uploading 576 B …
Deploy dep-3493c505ea9b4415b359 queued (upload), streaming logs…
09:36:21 ==> Starting deploy dep-3493c505ea9b4415b359 (trigger: upload)
09:36:21 ==> Extracting uploaded source archive
09:36:21 ==> Extracted 2 files (791 B)
09:36:21 ==> Detected Node.js runtime
09:36:21 ==> Generated Dockerfile.ferry for the Node.js runtime
09:36:21 ==> Building image ferry/node-hello:dep-3493c505ea9b4415b359
09:36:21 #1 [internal] load build definition from Dockerfile.ferry
…
09:36:21 ==> Build successful 🎉
09:36:21 ==> Using port 10000 (default port)
09:36:21 ==> Limits: 512 MiB memory, 1 CPU per instance
09:36:21 ==> Starting 1 instance(s)
09:36:21 ==> Started instance 82e2be (port 10000, published on 127.0.0.1:62694)
09:36:21 ==> Waiting for 1 instance(s) to become healthy: the port must accept TCP connections (timeout 120s)
09:36:21 [82e2be] > node-hello@1.0.0 start
09:36:21 [82e2be] > node server.js
09:36:22 [82e2be] node-hello listening on :10000
09:36:23 ==> Health check passed
09:36:23 ==> Routing traffic to the new instance(s)
09:36:23 ==> Your service is live 🎉
09:36:23 ==> Available at http://node-hello.localhost:8080
Deploy dep-3493c505ea9b4415b359 is live at http://node-hello.localhost:8080Read more
| Step | Detail | Page |
|---|---|---|
| Runtime | The Dockerfile for Node.js uses node:22-alpine, npm install, then npm start. | Builds & runtimes |
| Port | server.js reads the PORT variable. | The port of your app |
| Limits | The Limits line shows them. | Resource limits |
| Traffic | The test is: the port must accept connections. | Deploys |
The command is ferry up.