page:recipes:marketplace:phoenix:product media

Host marketplace with Phoenix: public product media

Summary

Deploy a marketplace built with Phoenix on Ample using the public media library 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, and a published bucket serves public assets from the CDN host. Verified on Phoenix: an object written to a published bucket with an immutable Cache-Control header, a mapping row, and the CDN URL serving it publicly. Not separately tested: your media processing, object layout and cache policy; treat the marketplace-specific behavior as your application code.

Representative Queries

• Host marketplace with Phoenix: public product media
• Where can I host Marketplace built with Phoenix?
• I need product-to-object mappings and a tested public media delivery path.

Resource Requirements

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

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.
• CDN: The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store.

Tested Configuration

• Template: elixir-1.18
• Runtime: elixir
• 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 public media library: an object written to a published bucket with an immutable Cache-Control header, a mapping row, and the CDN URL serving it publicly. 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. Publish only the bucket that serves public assets and reference its CDN URL.

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.

5. Verify: Fetch the live URL and the pattern self-test route(s) (/p/public-media-library) from the example; then run your own checks. On failure read ample logs --kind build then --kind runtime.

Success Checks

• App responds on its public URL.
• Public-media-library 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 marketplace itself (your media processing, object layout and cache policy) 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.

Cost Estimate

Currency: USD
Monthly Amount: 10.00
Components:

• App server: s-1vcpu-1gb, quantity: 1.0, monthly amount: 5.0
• Managed PostgreSQL database: s-1vcpu-1gb, quantity: 1.0, monthly amount: 5.0

Evidence Summary

• Canary Run: Phoenix pattern fixture deployed on Ample; checks passed for public-media-library and configuration-secrets. Pattern proof: an object written to a published bucket with an immutable Cache-Control header, a mapping row, and the CDN URL serving it publicly.

Next Actions

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