Stack detection
Deployxa reads your repository and picks the runtime, build and start commands. Override any of them in project settings.
Deploy Go on Deployxa.
Compile and deploy Go web services as small container images with HTTPS and health checks.
- 01Detected fromgo.mod
- 02RuntimeCompiled binary
- 03Build commandgo build -o server .
- 04Start command./server
- 05Port8080
- 06HTTPSLet's Encrypt
01 / Quickstart
Deploy from your terminal.
Install the CLI and deploy the Go project in your current directory, or connect the repository in the console for push-to-deploy.
- Typical database: PostgreSQL or MySQL
- Build and start commands can be overridden
- Secrets stay out of build logs
$ npm install -g @deployxa/cli$ deployxa login$ deployxa deploy
02 / Guide
How Go goes to production.
- 01 /
Build
Deployxa finds go.mod and compiles your binary.
- 02 /
Go live
The binary runs in a minimal image, health-checked and served over HTTPS.
03 / Configuration
Environment variables.
Set these in project settings. Values are never written to build logs.
| Variable | Purpose | Example |
|---|---|---|
PORT | Port the server listens on | 8080 |
04 / Included
What every deploy gets.
Isolated builds
Every push builds in its own sandbox with cached dependencies and layers.
Managed databases
Attach PostgreSQL, MySQL or Redis and the connection details are injected as environment variables.
HTTPS by default
Every deploy gets a deployxa.online URL with a Let's Encrypt certificate; custom domains too.
Health-checked releases
Traffic only switches to a release that passes its health check, and earlier releases stay available for rollback.
Push to deploy
Connect GitHub, GitLab or Bitbucket and each push to your branch ships a new release.
05 / FAQ
Go questions.
Are cgo dependencies supported?
Yes, as long as the C libraries are available in the build. Use a Dockerfile if you need extra system packages.