page:recipes:reporting dashboard:phoenix:data exports

Host Reporting Dashboard with Phoenix: Data Exports

Deploy a reporting dashboard built with Phoenix on Ample using the generated downloads 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: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3). Not separately tested: your export formats, retention policy and entitlement model; treat the reporting dashboard-specific behavior as your application code.

Representative Queries

• Host reporting dashboard with Phoenix: data exports
• Where can I host Reporting dashboard built with Phoenix?
• I need a scoped export format, artifact generation and authorized download procedure.

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.

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 generated downloads: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3). 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.
5. Verify: Fetch the live URL and the pattern self-test route(s) (/p/generated-downloads) from the example; then run your own checks. On failure read ample logs --kind build then --kind runtime.

Examples

• Phoenix pattern fixture: Multi-pattern Phoenix app whose generated downloads module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

Success Checks

• app responds on its public URL
• generated-downloads 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.

Cost Estimate

• Monthly Amount: $10.0
• Components:
  • app server: 1 x s-1vcpu-1gb: $5.0
  • managed PostgreSQL database: 1 x s-1vcpu-1gb: $5.0

Next Actions

• Browse the catalog index: GET /v1/catalog
• Search published recipes: POST /v1/catalog/search
• Prepare a deployment plan: POST /v1/catalog/plan
• Read existing agent authentication setup: GET /mcp/setup
• Browse Reporting dashboard: GET /v1/catalog/nodes/workload%3Areporting-dashboard
• Browse Phoenix: GET /v1/catalog/nodes/stack%3Aframework-phoenix
• Browse Generated downloads: GET /v1/catalog/nodes/pattern%3Agenerated-downloads
• Browse Deploy web app: GET /v1/catalog/nodes/intent%3Adeploy-web-app