Section 1
How deployment works
When you trigger a deploy — from a Git push or a ZIP upload — the platform executes these eight steps in sequence. Understanding this pipeline explains most deployment behaviour and error messages.
01
Clone / extract
Git repo or ZIP
02
Allocate port
Stable across deploys
03
Set environment
User + platform vars
04
Build
BUILD_COMMANDS
05
Start app
RUN_COMMAND executed
06
Go live
Public URL assigned
07
Enable HTTPS
Auto certificate
08
Health check
Ping → deployed ✓
| # | Step | Detail |
|---|---|---|
01 | Clone / extract | Git repo or ZIP |
02 | Allocate port | Stable across deploys |
03 | Set environment | User + platform vars |
04 | Build | BUILD_COMMANDS |
05 | Start app | RUN_COMMAND executed |
06 | Go live | Public URL assigned |
07 | Enable HTTPS | Auto certificate |
08 | Health check | Ping → deployed ✓ |
Port binding is the #1 deploy failure. Your app must listen on
0.0.0.0:$APP_PORT — not localhost, not a hard-coded port. The platform allocates the port; you read it from the environment.