page:recipes:vendor portal:phoenix:public profiles

Host vendor portal with Phoenix: public profile assets

Summary

Deploy a vendor portal built with Phoenix on Ample using the public image delivery 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: public objects in a published bucket served from the CDN URL, kept separate from private objects in an unpublished bucket that require authorization (private=ok only for the allowed role). Not separately tested: your image processing and profile-media rules; treat the vendor portal-specific behavior as your application code.

Representative Queries

• Host vendor portal with Phoenix: public profile assets
• Where can I host Vendor portal built with Phoenix?
• I need separate public profile media from private data, with CDN cache rules.

Resource Requirements

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

Infrastructure Requirements

1. Compute
   • Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.
2. Postgres
   • Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.
3. S3-compatible object storage
   • The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store.

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 and a second, published bucket for public assets (CDN_*)
• An Ample account token with servers:write, databases:read, buckets:read

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
   • 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.
4. Deploy
   • Run the synchronous deploy once and read the result (exit 0 live, 1 failed, 2 blocked).
5. Verify
   • Fetch the live URL and the pattern self-test route(s) from the example; then run your own checks.

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 vendor portal itself (your image processing and profile-media rules) is application code and was not separately tested.

Cost Estimate

• Monthly Cost: $10.00
  • App Server: $5.00
  • Managed PostgreSQL Database: $5.00
  • Always-on monthly price is for the tested sizes.