# Host campaign site with Phoenix: bulk content imports

Deploy a campaign site built with Phoenix on Ample using the bulk import staging 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, a private S3-compatible bucket holds objects with credentials delivered as encrypted environment variables. Verified on Phoenix: a CSV staged as an object, row-level validation with per-row errors recorded, and a restart-safe import keyed by import id (imported=2 rejected=1 restart=ok). Not separately tested: your import format, mapping and conflict rules; treat the campaign site-specific behavior as your application code.

## Representative Queries
- Host campaign site with Phoenix: bulk content imports
- Where can I host Campaign site built with Phoenix?
- I need a staged import format, validation procedure and import recovery workflow.

## Resource Requirements
- primitive:compute
- primitive:postgres
- primitive:s3-compatible-object-storage

## 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 bulk import staging: a CSV staged as an object, row-level validation with per-row errors recorded, and a restart-safe import keyed by import id (imported=2 rejected=1 restart=ok). 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.
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.
   ```shell
   ample deploy . --name  --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=...
   ```
5. **Verify**  
   Fetch the live URL and the pattern self-test route(s) (/p/bulk-import-staging) from the example; then run your own checks. On failure read `ample logs  --kind build` then `--kind runtime`.
   ```shell
   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 import format, mapping and conflict rules) is application code and was not separately tested; the pattern checks are what was verified.

## Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 10.0
- **Components**:
  - app server (s-1vcpu-1gb): $5.00
  - managed PostgreSQL database (s-1vcpu-1gb): $5.00
- **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
- **Canary Run**: Phoenix pattern fixture deployed on Ample; checks passed for bulk-import-staging and configuration-secrets. 
- **Observed At**: 2026-09-20T23:45:31Z

## Next Actions
- **[Browse the catalog index](https://api.ample.computer/v1/catalog)**  
- **[Search published recipes by intent, stack and constraints](https://api.ample.computer/v1/catalog/search)**  
- **[Prepare a side-effect-free deployment plan for an authorized project](https://api.ample.computer/v1/catalog/plan)**  
- **[Read the existing agent authentication setup](https://api.ample.computer/mcp/setup)**  
- **[Browse Campaign site](https://api.ample.com/computer/v1/catalog/nodes/workload%3Acampaign-site)**  
- **[Browse Phoenix](https://api.ample.com/computer/v1/catalog/nodes/stack%3Aframework-phoenix)**  
- **[Browse Bulk import staging](https://api.ample.com/computer/v1/catalog/nodes/pattern%3Abulk-import-staging)**  
- **[Browse Deploy web app](https://api.ample.com/computer/v1/catalog/nodes/intent%3Adeploy-web-app)**