Docs menu
Getting started with Go
Deploy a minimal Go web app to Primcloud end-to-end using a sample repo, in about five minutes.
On this page
Deploy a small Go web app to Primcloud: fork a sample repo, import it, watch the build, and open the app at its *.primcloud.app URL. It takes about five minutes.
Before you start#
You'll need:
- A Primcloud account. Standard accounts have no monthly fee; compute is metered by the minute once you deploy, from around $5/mo for the smallest app.
- A git provider connected to your Primcloud account; see Source Control.
- Optional: Go 1.23 or newer installed locally, if you want to run the sample or make changes before deploying.
The sample app#
For this guide, use Heroku's heroku/go-getting-started repo. It's a minimal Gin-based web app that builds on Primcloud with no changes. Fork it into an account you've connected to Primcloud.
1. Create the application#
Hit Import Git Repository on the applications list, then:
- Select your fork of
go-getting-started. - Configure the branch (
main) and a region. - Verify the commit and hit Import.
2. Deploy#
The first deployment starts as soon as the app is created, and its build log streams live:
- Detection. Primcloud sees the
go.modat the repo root and picks the Go toolchain. - Build. The Go SDK is installed at the version requested by
go.mod. The build downloads the modules the app depends on and runsgo install -tags herokuagainst everymainpackage it finds. For the sample, that's a single binary namedgo-getting-started. - Start. Primcloud reads the sample's
Procfile, which declaresweb: go-getting-started, and starts that process.
When the deployment's Rollout phase shows Complete, the app is live.
3. Reach the app#
Click the *.primcloud.app URL in the dashboard header to open the app.
If it doesn't come up:
- Deployments: the build log has the raw output from
go install. - Logs: runtime output from your app streams there, including any startup errors.
- Confirm the app binds to the port in
$PORT. Primcloud sets this to the constant5000on thewebformation; the sample reads it viaos.Getenv("PORT")before callingrouter.Run.
Where to go next#
- Deploying a different Go app: Go on Primcloud for detection, package selection, and process type inference.
- Pinning to a specific Go version: Runtime versions.
- Using a private module: Package managers.
- Building only certain binaries or vendoring dependencies: Customizing the build.
- Something breaking: Troubleshooting Go.