Stack detection
Deployxa reads your repository and picks the runtime, build and start commands. Override any of them in project settings.
Deploy Docker on Deployxa.
Deploy any Dockerfile, including multi-stage builds, with layer caching, a custom port, health checks and HTTPS.
- 01Detected fromDockerfile
- 02RuntimeOCI container
- 03Dockerfile./Dockerfile
- 04Portthe port you EXPOSE
- 05HTTPSLet's Encrypt
01 / Quickstart
Deploy from your terminal.
Install the CLI and deploy the Docker project in your current directory, or connect the repository in the console for push-to-deploy.
- Typical database: Any managed database
- 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 Docker goes to production.
- 01 /
Build
Your Dockerfile is built with layer caching.
- 02 /
Run
The container runs with its own resource limits and the port you set.
- 03 /
Go live
Traffic switches once the container passes its health check.
03 / Configuration
Environment variables.
Set these in project settings. Values are never written to build logs.
| Variable | Purpose | Example |
|---|---|---|
PORT | Port the container 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
Docker questions.
When should I use a Dockerfile?
When your stack is not detected automatically or needs system packages. Add a Dockerfile to the repository and Deployxa builds that.