## Host storefront with Phoenix: inventory imports

### Summary
Deploy a storefront 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 storefront-specific behavior as your application code.

### Representative Queries
- Host storefront with Phoenix: inventory imports
- Where can I host Storefront built with Phoenix?
- I need an inventory import contract, staging objects and row-level error handling.

### Parent Requirements
- **Workload**: Storefront
- **Framework**: Phoenix
- **Release Status**: published
- **Support Status**: verified
- **Execution Status**: ready

### Resource Requirements
- Compute
- PostgreSQL
- S3-compatible object storage

### 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. **S3-compatible object storage**: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

### 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

### Tested Configuration
- **Template**: elixir-1.18
- **Size**: s-1vcpu-1gb
- **Install**: mix local.hex --force && mix local.rebar --force && MIX_ENV=prod mix deps.get --only prod
- **Build**: MIX_ENV=prod mix compile && MIX_ENV=prod mix release --overwrite
- **Start**: PHX_SERVER=true _build/prod/rel/$(ls _build/prod/rel | head -n 1)/bin/$(ls _build/prod/rel | head -n 1) start

### 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

### Examples
1. **Phoenix pattern fixture**: Multi-pattern Phoenix app whose bulk import staging module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

### Success Checks
- App responds on its public URL.
- Bulk-import-staging self-test.

### 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 storefront 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
- **Basis**: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
- **Components**:
  - App server: s-1vcpu-1gb
  - Managed PostgreSQL database: s-1vcpu-1gb

### Next Actions
1. Browse the catalog index.
2. Search published recipes by intent, stack and constraints.
3. Prepare a side-effect-free deployment plan for an authorized project.
4. Read the existing agent authentication setup.