## Host campaign site with Phoenix: public-site delivery

### Summary
Deploy a campaign 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. Not separately tested: your site content and build; treat the campaign site-specific behavior as your application code.

### Representative Queries
- Host campaign site with Phoenix: public-site delivery
- Where can I host Campaign site built with Phoenix?
- I need an explicit origin-to-CDN delivery path and a tested public content build.

### Resource Requirements
- **Compute**
- **CDN**

### Infrastructure Requirements
1. **Compute**  
   - Status: verified  
   - Summary: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.  
   - [More Info](/discover/primitive/compute)

2. **CDN**  
   - Status: verified  
   - Summary: The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store.  
   - [More Info](/discover/primitive/cdn)

### Prerequisites
- 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 create` with its credentials passed as encrypted S3_* environment variables.  
- An Ample account token with servers:write, buckets:read.

### Workflow Steps
1. **Build and start**  
   - Body: 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.

2. **Wire object storage**  
   - Body: 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.

3. **Deploy**  
   - Body: Run the synchronous deploy once and read the result (exit 0 live, 1 failed, 2 blocked). Re-running with no change is a no-op.  
   - Command: ample deploy . --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=...

4. **Verify**  
   - Body: 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  --kind build` then `--kind runtime`.  
   - Command: ample logs  --kind build

### Limitations
- Verified on the elixir-1.18 template at s-1vcpu-1gb with the example fixture; other sizes, templates and Phoenix major versions are not verified.  
- The campaign site itself (your site content and build) is application code and was not separately tested; the pattern checks are what was verified.
- Region, compliance attestations and request-duration limits are unknown and not claimed.
- Apps auto-pause when idle and wake on the next request; always-on is an operator setting, not a plan feature.

### Success Checks
1. **app responds on its public URL**  
   - Kind: http_get  
   - Path: /  
   - Expect: ample canary phoenix patterns

2. **versioned-static-assets self-test**  
   - Kind: http_get  
   - Path: /p/versioned-static-assets  
   - Expect: a CDN URL whose content is served publicly.

### Cost Estimate
- **Monthly Amount**: $5.00  
   - Basis: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty  
   - Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.

### Evidence Summary
1. **Phoenix pattern fixture**  
   - Summary: Deployed on Ample; checks passed for versioned-static-assets and configuration-secrets.  
   - Observed At: 2026-09-20T23:45:31Z

2. **The same Phoenix app deployed with a --release-command migration**  
   - Summary: The marker it created was readable after activation.  
   - Observed At: 2026-09-20T23:45:31Z

### Next Actions
- [Browse the catalog index](#)  
- [Search published recipes by intent, stack and constraints](#)  
- [Prepare a side-effect-free deployment plan for an authorized project](#)  
- [Read the existing agent authentication setup](#)  
- [Browse Campaign site](#)  
- [Browse Phoenix](#)  
- [Browse Public web service](#)  
- [Browse Deploy web app](#)

### Formats
- [HTML Version](/content/recipes/campaign-site/phoenix/public-site/index.html)  
- [Markdown Version](/content/recipes/campaign-site/phoenix/public-site.md)  
- [JSON Version](https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Acampaign-site%3Aphoenix%3Apublic-site)