### Host company website with Phoenix: public-site delivery

Deploy a company website 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 company website-specific behavior as your application code.

#### Summary
- **Family**: Workload recipe  
- **Framework**: Phoenix  
- **Workload**: Company website  
- **Release Status**: published  
- **Support Status**: verified  
- **Execution Status**: ready

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

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

#### 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 company website itself (your site content and build) is application code and was not separately tested; the pattern checks are what was verified.

#### Workflow Steps
1. **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.
2. **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.
3. **Deploy**  
   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.  
   ```bash  
   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**  
   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`.  
   ```bash  
   ample logs  --kind build  
   ```

#### Success Checks
- App responds on its public URL.
- Versioned-static-assets self-test.

#### Cost Estimate
- **Currency**: USD  
- **Monthly Amount**: 5.0  
- **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.