Host client portal with Phoenix: application activity history

Summary

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

Representative Queries

• Host client portal with Phoenix: application activity history
• Where can I host Client portal 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

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

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

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

Success Checks

1. App responds on its public URL

   • Kind: http_get
   • Path: /
   • Expect: ample canary phoenix patterns

2. 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 client portal 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.0
• Authoritative: true
• Basis: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
• Components:
  • App server
    • Size: s-1vcpu-1gb
    • Quantity: 1.0
    • Monthly Amount: 5.0
  • Managed PostgreSQL database
    • Size: s-1vcpu-1gb
    • Quantity: 1.0
    • Monthly Amount: 5.0
• 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

• Kind: canary_run

  • Summary: Phoenix pattern fixture deployed on Ample (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); checks passed for transactional-workflows and configuration-secrets. Pattern proof: 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).
  • Observed At: 2026-09-20T23:45:31Z
  • Implementation Revision: 4d1511e574302f3904b75088bd4048a0975218b3-dirty (CLI 0.1.21)
  • Expires At: 2027-03-19T23:45:31Z
  • Scope: {"checks":["/p/transactional-workflows"],"pattern":"pattern:transactional-workflows","template":"elixir-1.18"}

• Kind: canary_run

  • Summary: 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
  • Scope: {"pattern":"pattern:transactional-workflows"}

Last Verified At

• Date: 2026-09-20T23:45:31Z

MCP Binding

• Registry Reference: mcp:ample_deploy
• Tool Name: ample_deploy
• Schema Hash: 876465fce906da0c224d62961d3343064108ebe30af80cf1b87094974e948853
• Observed At: 2026-09-21T03:19:59.461917+00:00
• Implementation Revision: 49962bcade4f
• Required Scopes: servers:write, databases:read
• Binding State: current

Unknowns

• Region availability is unknown until a verified region fact is recorded.
• Compliance attestations are unknown; none are claimed.

Formats

• HTML: https://ample.computer/recipes/client-portal/phoenix/activity-history
• Markdown: https://ample.computer/recipes/client-portal/phoenix/activity-history.md
• JSON: https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Aclient-portal%3Aphoenix%3Aactivity-history

Next Actions

1. Browse the catalog index

   • Action ID: browse-catalog
   • Method: GET
   • Relative Path: /v1/catalog
   • Requires Authentication: false
   • Requires Approval: false

2. Search published recipes by intent, stack and constraints

   • Action ID: search-recipes
   • Method: POST
   • Relative Path: /v1/catalog/search
   • Requires Authentication: false
   • Requires Approval: false

3. Prepare a side-effect-free deployment plan for an authorized project

   • Action ID: plan:page:recipes:client-portal:phoenix:activity-history
   • Method: POST
   • Relative Path: /v1/catalog/plan
   • Requires Authentication: true
   • Requires Approval: false

4. Read the existing agent authentication setup

   • Action ID: auth-setup
   • Method: GET
   • Relative Path: /mcp/setup
   • Requires Authentication: false
   • Requires Approval: false

5. Browse Client portal

   • Action ID: browse:workload:client-portal
   • Method: GET
   • Relative Path: /v1/catalog/nodes/workload%3Aclient-portal
   • Requires Authentication: false
   • Requires Approval: false

6. Browse Phoenix

   • Action ID: browse:stack:framework-phoenix
   • Method: GET
   • Relative Path: /v1/catalog/nodes/stack%3Aframework-phoenix
   • Requires Authentication: false
   • Requires Approval: false

7. Browse Transactional workflows

   • Action ID: browse:pattern:transactional-workflows
   • Method: GET
   • Relative Path: /v1/catalog/nodes/pattern%3Atransactional-workflows
   • Requires Authentication: false
   • Requires Approval: false

8. Browse Deploy web app

   • Action ID: browse:intent:deploy-web-app
   • Method: GET
   • Relative Path: /v1/catalog/nodes/intent%3Adeploy-web-app
   • Requires Authentication: false
   • Requires Approval: false