Features · Deploys & runtimes
Three ways in.
One pipeline.
However the code arrives, the same thing happens to it — and you can watch the whole thing while it runs.
However the code arrives
Push to a branch
Connect a repository and every push to the branch you're watching rebuilds and goes live.
From your machine
astrodock deploy uploads the working directory — useful for the thing
you haven't committed yet.
From an agent
The same CLI with a scoped key, streaming until it can report success or failure.
Runtimes
Node without config. Docker without limits.
Put a frontend and a server in a folder
The runtime works out the shape. The frontend is built and served as static files,
the server gets its own process, and requests under /api reach it on
the same origin — so there's no CORS to fight and no proxy to write.
Or ship a Dockerfile
Python, Go, Rust, a binary someone handed you. Astrodock builds the image, runs the container alongside everything else and gives it the whole subdomain. Bind the port you're given and answer a health check — that's the contract.
When it goes wrong
Failures you can
actually act on.
A deploy that's missing a required secret stops before it starts and names the variable. A build that fails keeps its full log, so you can read what the installer actually said — weeks later, long after the moment has passed.
Every build is kept. Nothing evaporates because a dashboard moved on.
$ astrodock deploy:watch Deploy blocked — set these first: - SLACK_WEBHOOK (no value) $ astrodock set-secret SLACK_WEBHOOK $ astrodock deploy:watch installing · building · publishing ✓ deploy success