## Host event registration with Phoenix: structured data imports

### Summary
Deploy an event registration 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 event registration-specific behavior as your application code.

### Representative Queries
- Host event registration with Phoenix: structured data imports
- Where can I host Event registration built with Phoenix?
- I need a workload-specific import mapping, conflict rules and restart behavior.

### Framework
- Phoenix

### Workload
- Event registration

### Release Status
- Published

### Support Status
- Verified

### Execution Status
- Ready

### 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 PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env).
- A bucket from `ample bucket create` with its credentials passed as encrypted S3_* environment variables.
- An Ample account token with servers:write, databases:read, buckets:read.

### 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.  
   Command: `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`.  
   Command: `ample logs --kind build`

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

- **Bulk-import-staging self-test**  
  - Kind: `http_get`  
  - Path: `/p/bulk-import-staging`  
  - Expect: `imported=2 rejected=1 restart=ok`

### 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 event registration itself (your import format, mapping and conflict rules) 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.
- Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified; apps and their databases are placed together.

### Cost Estimate
- Currency: USD  
- Monthly Amount: 10.0  
- Authoritative: true  
- 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.

### Evidence Summary
- Kind: `canary_run`  
  - Summary: Phoenix 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 bulk-import-staging and configuration-secrets. Pattern proof: 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).  
  - Observed At: 2026-09-20T23:45:31Z  
  - Implementation Revision: 4d1511e574302f3904b75088bd4048a0975218b3-dirty (CLI 0.1.21)  
  - Expires At: 2027-03-19T23:45:31Z

### Next Actions
- **Browse the catalog index**  
  - Action ID: `browse-catalog`  
  - Operation ID: `catalog_index`  
- **Search published recipes by intent, stack and constraints**  
  - Action ID: `search-recipes`  
  - Operation ID: `search_recipes`  
- **Prepare a side-effect-free deployment plan for an authorized project**  
  - Action ID: `plan:page:recipes:event-registration:phoenix:data-imports`  
  - Operation ID: `plan_deployment`  
- **Read the existing agent authentication setup**  
  - Action ID: `auth-setup`  
  - Operation ID: `existing_auth_setup`  
- **Browse Event registration**  
  - Action ID: `browse:workload:event-registration`  
  - Operation ID: `browse_node`  
- **Browse Phoenix**  
  - Action ID: `browse:stack:framework-phoenix`  
  - Operation ID: `browse_node`  
- **Browse Bulk import staging**  
  - Action ID: `browse:pattern:bulk-import-staging`  
  - Operation ID: `browse_node`  
- **Browse Deploy web app**  
  - Action ID: `browse:intent:deploy-web-app`  
  - Operation ID: `browse_node`