Stack detection
Deployxa reads your repository and picks the runtime, build and start commands. Override any of them in project settings.
Deploy Rust on Deployxa.
Deploy Rust web services built with Axum or Actix Web: cargo release builds with dependency caching, HTTPS and health checks.
- 01Detected fromCargo.toml
- 02RuntimeCompiled binary
- 03Build commandcargo build --release
- 04Start command./target/release/server
- 05HTTPSLet's Encrypt
01 / Quickstart
Deploy from your terminal.
Install the CLI and deploy the Rust project in your current directory, or connect the repository in the console for push-to-deploy.
- Typical database: PostgreSQL with SQLx or Diesel
- 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 Rust goes to production.
- 01 /
Build
cargo build --release compiles your service; dependency layers are cached between builds.
- 02 /
Go live
The binary is 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 |
|---|---|---|
RUST_LOG | Log level filter | info |
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
Rust questions.
Are builds cached?
Yes. Build layers are cached, so unchanged dependencies are not recompiled on every push.