page:recipes:inventory manager:phoenix:csv imports

Host inventory manager with Phoenix: CSV imports

Summary

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

Resource Requirements

• Compute (primitive:compute)
• Postgres (primitive:postgres)
• S3-compatible object storage (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.

   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.

   ample logs  --kind build
   

Prerequisites

• A Phoenix project that builds and starts with the documented commands.
• A PostgreSQL driver reading DATABASE_URL at runtime.
• A bucket from ample bucket create with its credentials passed as encrypted S3_* environment variables.
• An Ample account token.

Cost Estimate

• Currency: USD
• Monthly Amount: $10.00 Components:
  • App server: $5.00
  • Managed PostgreSQL database: $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.

Limitations

• Verified on the elixir-1.18 template at s-1vcpu-1gb with the example fixture.
• The inventory manager itself (your import format, mapping and conflict rules) is application code and was not separately tested.
• Apps auto-pause when idle and wake on the next request.

Examples

• Phoenix pattern fixture
  Multi-pattern Phoenix app whose bulk import staging module was checked live.

Success Checks

1. App responds on its public URL.
2. Bulk-import-staging self-test.