deploy go

net/http, gin, echo, anything that compiles. one binary, one server.

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-go
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 go

go.mod at the project root

what happens when you push

go build runs from main.go at the root, or from the first cmd/<name>/main.go for the standard multi-binary layout
listen on the PORT environment variable (it is set to 8080), on 0.0.0.0

sharp edges

several cmd folders? the first one found wins. keep one main, or put main.go at the root

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.