# Configure environment and secrets for Axum

Configuration and secrets for a Axum app on Ample. Verified on Axum: an --env value delivered encrypted and reported as present without being echoed (secret=set). Build and start: cargo build --release in the rust builder image (stable toolchain, Cargo.lock committed, pure-Rust dependencies), then the release binary on the ubuntu-24.04 template reading PORT and DATABASE_URL.

Verified November 5, 2026

## What it runs on

- [Computeverified](/content/discover/primitive/compute/index.html)
  Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.

## You need

- An Axum project (cargo build --release in the rust builder image (stable toolchain, Cargo.lock committed, pure-Rust dependencies), then the release binary on the ubuntu-24.04 template reading PORT and DATABASE_URL)

- An Ample account token with servers:write

## Exact tested configuration

- build cargo build --release
- run time rust
- sizes 1vcpu-2gb
- start ./$(ls target/release/*.d | grep -v '/lib' | head -n 1 | sed 's/\.d$//')
- template ubuntu-24.04

## Steps

1. **Build and start.** cargo build --release in the rust builder image (stable toolchain, Cargo.lock committed, pure-Rust dependencies), then the release binary on the ubuntu-24.04 template reading PORT and DATABASE_URL; the server must bind 0.0.0.0 on PORT.

2. **Pass values on deploy.** Use --env KEY=value (repeatable) or --env-file; values are encrypted at rest and reused on redeploys. Declare names only in ample.toml.

```
   $ ample deploy . --name <app-name> --public --env MY_SECRET=...
   ```

3. **Verify.** Fetch the live URL and /p/configuration-secrets on the example; on failure read the build and runtime logs.

```
   $ ample logs <deployment_id> --kind build
   ```

## How it was checked

✓ app responds on its public URL· http get/ → “ample canary axum patterns”

✓ configuration-secrets check from the example· http get/p/configuration-secrets → “see the pattern fixture checks”

## Evidence

1. November 5, 2026 · canary run

Axum pattern fixture deployed on Ample (cargo build --release in the rust builder image (stable toolchain, Cargo.lock committed, pure-Rust dependencies), then the release binary on the ubuntu-24.04 template reading PORT and DATABASE_URL); for this guide: an --env value delivered encrypted and reported as present without being echoed (secret=set).

## Tested examples

- **Axum pattern fixture.** Verified configuration and secrets on Axum.

## What it doesn’t cover

- Verified on the ubuntu-24.04 template at s-1vcpu-2gb.
