page:recipes:subscription content:phoenix:inventory imports

Host subscription content with Phoenix: inventory imports

Summary

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

Representative Queries

• Host subscription content with Phoenix: inventory imports
• Where can I host Subscription content built with Phoenix?
• I need an inventory import contract, staging objects and row-level error handling.

Resource Requirements

• primitive:compute
• primitive:postgres
• primitive:s3-compatible-object-storage

Infrastructure Requirements

• Compute: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
• 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.
• 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).
• 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 with servers:write, databases:read, buckets:read.

Workflow Steps

1. Build and start: Execute mix deps.get, MIX_ENV=prod mix compile, and mix release in the builder.
2. Implement the pattern on PostgreSQL: Copy the modular approach into your schema; keep migrations idempotent.
3. Wire object storage: Create the bucket(s), then pass endpoint, region, bucket and keys as --env values.
4. Deploy: Run the synchronous deploy once and read the result.
5. Verify: Fetch the live URL and test routes.

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

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

Limitations

• Verified on the elixir-1.18 template at s-1vcpu-1gb. Other sizes, templates and Phoenix major versions are not verified.
• The subscription content itself (your import format, mapping and conflict rules) was not separately tested.
• Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified.

Cost Estimate

• 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.

Evidence Summary

1. Canary run: Phoenix pattern fixture deployed on Ample; checks passed.
2. Canary run: The same Phoenix app deployed with a --release-command migration.

Unknowns

• Region availability and compliance attestations are unknown until verified.

Action Items

• Browse the catalog index.
• Search published recipes by intent, stack and constraints.
• Prepare a side-effect-free deployment plan for an authorized project.