## Host knowledge base with Phoenix: bulk content imports

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

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

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

### Examples
- **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
- **HTTP GET** - app responds on its public URL `path: /`, expect: `ample canary phoenix patterns`
- **HTTP GET** - bulk-import-staging self-test at path `/p/bulk-import-staging`, expect: `imported=2 rejected=1 restart=ok`

### Limitations
- Verified on the elixir-1.18 template at size s-1vcpu-1gb with the example fixture; other sizes, templates and Phoenix major versions are not verified.
- The knowledge base itself was not separately tested; the pattern checks are what was verified.

### Cost Estimate
- Monthly Amount: **$10.00 USD**  
  - **App server**: size **s-1vcpu-1gb**, quantity **1**, monthly amount **$5.00**  
  - **Managed PostgreSQL database**: size **s-1vcpu-1gb**, quantity **1**, monthly amount **$5.00**  
  **Note**: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

### Evidence Summary
- **Canary Run** - Phoenix pattern fixture deployed on Ample; checks passed for bulk-import-staging and configuration-secrets.

Last verified at: `2026-09-20T23:45:31Z`

### Next Actions
- **Browse the catalog index** - GET `/v1/catalog`
- **Search published recipes by intent, stack and constraints** - POST `/v1/catalog/search` with body `{ limit: 5, query: "Host knowledge base with Phoenix: bulk content imports" }` 
- **Prepare a side-effect-free deployment plan** - POST `/v1/catalog/plan` with body `{ inputs: {}, projectId: "", recipeId: "page:recipes:knowledge-base:phoenix:content-imports", recipeRevision: "r1" }` 
- **Read the existing agent authentication setup** - GET `/mcp/setup` 
- **Browse Knowledge base** - GET `/v1/catalog/nodes/workload%3Aknowledge-base` 
- **Browse Phoenix** - GET `/v1/catalog/nodes/stack%3Aframework-phoenix` 
- **Browse Bulk import staging** - GET `/v1/catalog/nodes/pattern%3Abulk-import-staging` 
- **Browse Deploy web app** - GET `/v1/catalog/nodes/intent%3Adeploy-web-app`