Host admin dashboard with Phoenix: application activity history

Summary

Deploy a admin dashboard built with Phoenix on Ample using the transactional workflows 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. Verified on Phoenix: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected). Not separately tested: your domain records, validation rules and concurrency policy; treat the admin dashboard-specific behavior as your application code.

Representative Queries

• Host admin dashboard with Phoenix: application activity history
• Where can I host Admin dashboard built with Phoenix?
• I need an application-owned event schema and tested history queries; not native platform audit logs.

Resource Requirements

• Compute
• Postgres

Infrastructure Requirements

• Compute
  Status: verified
  Summary: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
• Postgres
  Status: verified
  Summary: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

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)
• An Ample account token with servers:write, databases: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: The fixture's module implements transactional workflows: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected). Copy the approach into your schema; keep migrations idempotent and run them with --release-command.
3. 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. Command: ample deploy . --name --public
4. Verify: Fetch the live URL and the pattern self-test route(s) (/p/transactional-workflows) from the example; then run your own checks. On failure read ample logs --kind build then --kind runtime. Command: ample logs --kind build

Examples

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

Success Checks

• App responds on its public URL:
  Kind: http_get
  Path: /
  Expect: ample canary phoenix patterns
• Transactional-workflows self-test:
  Kind: http_get
  Path: /p/transactional-workflows
  Expect: tx=ok history=2 conflict=rejected

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 admin dashboard itself (your domain records, validation rules and concurrency 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.
• Apps auto-pause when idle and wake on the next request; always-on is an operator setting, not a plan feature.
• Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified; apps and their databases are placed together.

Cost Estimate

• Currency: USD
• Monthly Amount: $10.00
• Authoritative: true
• Basis: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
• Components:
  • Name: app server
    Size: s-1vcpu-1gb
    Quantity: 1.0
    Monthly Amount: $5.00
  • Name: managed PostgreSQL database
    Size: s-1vcpu-1gb
    Quantity: 1.0
    Monthly Amount: $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.

Evidence Summary

• Canary Run: Phoenix pattern fixture deployed on Ample; checks passed for transactional-workflows and configuration-secrets.
  • Observed At: 2026-09-20T23:45:31Z
  • Implementation Revision: 4d1511e574302f3904b75088bd4048a0975218b3-dirty (CLI 0.1.21)
  • Expires At: 2027-03-19T23:45:31Z
• Canary Run: The same Phoenix app deployed with a --release-command migration; the marker it created was readable after activation.
  • Observed At: 2026-09-20T23:45:31Z
  • Implementation Revision: 4d1511e574302f3904b75088bd4048a0975218b3-dirty (CLI 0.1.21)
  • Expires At: 2027-03-19T23:45:31Z

Formats

• HTML Format
• Markdown Format
• JSON Format

Next Actions

• Browse the catalog index
  • Operation ID: catalog_index
  • Method: GET
  • Relative Path: /v1/catalog
• Search published recipes by intent, stack and constraints
  • Operation ID: search_recipes
  • Method: POST
  • Relative Path: /v1/catalog/search
  • Parameters: { "body": { "limit": 5, "query": "Host admin dashboard with Phoenix: application activity history" } }
• Prepare a side-effect-free deployment plan for an authorized project
  • Operation ID: plan_deployment
  • Method: POST
  • Relative Path: /v1/catalog/plan
  • Parameters: { "body": { "inputs": {}, "projectId": "", "recipeId": "page:recipes:admin-dashboard:phoenix:activity-history", "recipeRevision": "r1" } }
• Read the existing agent authentication setup
  • Operation ID: existing_auth_setup
  • Method: GET
  • Relative Path: /mcp/setup
• Browse Admin dashboard
  • Operation ID: browse_node
  • Method: GET
  • Relative Path: /v1/catalog/nodes/workload%3Aadmin-dashboard
• Browse Phoenix
  • Operation ID: browse_node
  • Method: GET
  • Relative Path: /v1/catalog/nodes/stack%3Aframework-phoenix
• Browse Transactional workflows
  • Operation ID: browse_node
  • Method: GET
  • Relative Path: /v1/catalog/nodes/pattern%3Atransactional-workflows
• Browse Deploy web app
  • Operation ID: browse_node
  • Method: GET
  • Relative Path: /v1/catalog/nodes/intent%3Adeploy-web-app