Host documentation site with Phoenix: public-site delivery · Ample Computer
Host documentation site with Phoenix: public-site delivery
Deploy a documentation site built with Phoenix on Ample using the public web service pattern. Compute runs the app in an isolated microVM behind a public HTTPS URL, and a published bucket serves public assets from the CDN host. Verified on Phoenix: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL alongside the app's own public HTTPS URL. The documentation site-specific behavior (your site content and build) is your application code on that verified basis.
Verified\nNovember 6, 2026
What it runs on
Computeverified \nApps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.
CDNverified \nA published bucket's objects are served from its public URL; set Cache-Control when uploading to control caching. App responses are served by the app.
You need
A Phoenix project that builds and starts with the documented commands (mix deps.get, MIX_ENV=prod mix compile and mix release in the builder, then the release bin script with PHX_SERVER=true on the elixir-1.18 template; PORT, DATABASE_URL and SECRET_KEY_BASE read in config/runtime.exs)
A bucket from
ample bucket createwith its credentials passed as encrypted S3_* environment variablesAn Ample account token with servers:write, buckets:read
Exact tested configuration
build \nMIX_ENV=prod mix compile && MIX_ENV=prod mix release --overwrite
install \nmix local.hex --force && mix local.rebar --force && MIX_ENV=prod mix deps.get --only prod
runtime elixir
sizes - 1vcpu-1gb
start \nPHX_SERVER=true _build/prod/rel/$(ls _build/prod/rel | head -n 1)/bin/$(ls _build/prod/rel | head -n 1) start
template elixir-1.18
Steps
Build and start. mix deps.get, MIX_ENV=prod mix compile and mix release in the builder, then the release bin script with PHX_SERVER=true on the elixir-1.18 template; PORT, DATABASE_URL and SECRET_KEY_BASE read in config/runtime.exs. The server must bind 0.0.0.0 on PORT.
Wire object storage. Create the bucket(s), then pass endpoint, region, bucket and keys as --env values. Use path-style addressing. Keep private data in an unpublished bucket. Publish only the bucket that serves public assets and reference its CDN URL.
Deploy. Run the synchronous deploy once and read the result (exit 0 live, 1 failed, 2 needs an answer first). Re-running with no change is a no-op.
$ ample deploy . --name <app-name> --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=... --env CDN_PUBLIC_URL=...
- Verify. Fetch the live URL and the pattern self-test route(s) (/p/versioned-static-assets) from the example; then run your own checks. On failure read
ample logs <deployment_id> --kind buildthen--kind runtime.
$ ample logs <deployment_id> --kind build
How it was checked
✓ app responds on its public URL · http get/ → “ample canary phoenix patterns” \n✓ versioned-static-assets self-test · http get/p/versioned-static-assets → “a CDN URL whose content is served publicly”
Evidence
November 6, 2026 · canary run \nPhoenix pattern fixture deployed on Ample (mix deps.get, MIX_ENV=prod mix compile and mix release in the builder, then the release bin script with PHX_SERVER=true on the elixir-1.18 template; PORT, DATABASE_URL and SECRET_KEY_BASE read in config/runtime.exs); checks passed for versioned-static-assets and configuration-secrets. Pattern proof: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL alongside the app's own public HTTPS URL.
November 6, 2026 · canary run \nThe same Phoenix app deployed with a --release-command migration; the marker it created was readable after activation.
Tested examples
- Phoenix pattern fixture. Multi-pattern Phoenix app whose public web service module was checked live; the module is under tests/deploy-canaries/_pattern-modules.
What it doesn’t cover
Verified on the elixir-1.18 template at s-1vcpu-1gb with the example fixture.
The pattern checks verified the platform side; the documentation site itself (your site content and build) is your application code.
Buckets speak the standard S3 API (PutObject and GetObject with path-style addressing are checked by the fixture);
ample bucket upload-urlreturns presigned upload URLs.The CDN serves published-bucket objects; control caching with Cache-Control on upload and versioned keys.