deploy fastify
fastify servers run as-is. no build step unless you have one.
the whole thing
curl -fsSL https://pushto.host/install | sh # or: brew install mydude-industries/tap/pushto · npm i -g @pushto/cli pushto login pushto init my-fastify pushto
that last bare pushto is the deploy. on windows, the install line is irm https://pushto.host/install.ps1 | iex in powershell. live at https://<your-name>.pushto.host with https. we build it and run it as a server. you never touch the machinery. runs on the free tier too — your one free app can be a server; it naps after a quiet spell and wakes on the next visit. $13/mo lifts the one-project cap and keeps apps always awake.
how we know it's fastify
- fastify in the dependencies of your root package.json
what happens when you push
- your start script runs as-is. a build script runs first only if you have one
- listen on process.env.PORT (it is set to 8080), and pass host: "0.0.0.0" to listen()
sharp edges
- package.json needs a start script
- fastify binds 127.0.0.1 by default, which is unreachable from outside. set host: "0.0.0.0"
deploying from an agent?
claude code and cursor can run all of this for you: connect your agent. the short machine-readable version of this site lives at https://pushto.host/llms.txt.
something off? run pushto doctor, or see all supported frameworks.