# Host campaign site with Phoenix: Postgres-backed content

Deploy a campaign site built with Phoenix on Ample using the relational records pattern. Compute runs the app in an isolated microVM behind a public HTTPS URL, a managed PostgreSQL 16 database is auto-provisioned and injected as DATABASE_URL, and a published bucket serves public assets from the CDN host. Verified on Phoenix: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true). Not separately tested: your record schema, states and access rules; treat the campaign site-specific behavior as your application code.

## Representative Queries
- Host campaign site with Phoenix: Postgres-backed content
- Where can I host Campaign site built with Phoenix?
- I need a content schema, publishing workflow and cache behavior after content updates.

## Resource Requirements
- primitive:compute
- primitive:postgres
- primitive:cdn

## Infrastructure Requirements
1. **Compute**: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
2. **Postgres**: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.
3. **CDN**: The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store.

## 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. **Implement the pattern on PostgreSQL**: The fixture's module implements relational records: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true). Copy the approach into your schema; keep migrations idempotent and run them with --release-command.
3. **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.
4. **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. Command: `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=...`
5. **Verify**: Fetch the live URL and the pattern self-test route(s) (/p/relational-records) from the example; then run your own checks. On failure read `ample logs  --kind build` then `--kind runtime`. Command: `ample logs  --kind build`

## Examples
- **Phoenix pattern fixture**: Multi-pattern Phoenix app whose relational records module was checked live; the module is under `tests/deploy-canaries/_pattern-modules`.

## Success Checks
- App responds on its public URL (http_get, path: /, expect: `ample canary phoenix patterns`).
- Relational-records self-test (http_get, path: /p/relational-records, expect: `records=ok transitions=true isolation=true`).

## 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 record schema, states and access rules) is application code and was not separately tested; the pattern checks are what was verified.

## Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 10.0
- **Basis**: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty.
  - **Components**:
    - App server, size: s-1vcpu-1gb, quantity: 1.0, monthly Amount: 5.0
    - Managed PostgreSQL database, size: s-1vcpu-1gb, quantity: 1.0, 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.