page:recipes:knowledge base:phoenix:public site

Host Knowledge Base with Phoenix: Public-Site Delivery

Summary

Deploy a knowledge base built with Phoenix on Ample using the public web service pattern. Compute runs the app in an isolated microVM behind a public HTTPS URL, and a published bucket serves public assets from the CDN host. Verified on Phoenix: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL alongside the app's own public HTTPS URL. Not separately tested: your site content and build; treat the knowledge base-specific behavior as your application code.

Representative Queries

• Host knowledge base with Phoenix: public-site delivery
• Where can I host Knowledge base built with Phoenix?
• I need an explicit origin-to-CDN delivery path and a tested public content build.

Resource Requirements

• Compute
• CDN

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.
   More Info

2. CDN
   Status: verified
   Summary: The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store.
   More Info

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 bucket from ample bucket create with its credentials passed as encrypted S3_* environment variables
• An Ample account token with servers:write, buckets:read

Tested Configuration

• Template: elixir-1.18
• Runtime: elixir
• Size: s-1vcpu-1gb
• Install Command: mix local.hex --force && mix local.rebar --force && MIX_ENV=prod mix deps.get --only prod
• Build Command: MIX_ENV=prod mix compile && MIX_ENV=prod mix release --overwrite
• Start Command: 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. 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.

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.

   ample deploy . --name  --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=... --env CDN_PUBLIC_URL=...
   

4. Verify
   Fetch the live URL and the pattern self-test route(s) (/p/versioned-static-assets) from the example; then run your own checks. On failure read ample logs --kind build then --kind runtime.

   ample logs --kind build
   

Examples

• Phoenix Pattern Fixture
  Multi-pattern Phoenix app whose public web service 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

• Versioned-Static-Assets Self-Test
  Kind: http_get
  Path: /p/versioned-static-assets
  Expect: a CDN URL whose content is served publicly

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 knowledge base itself (your site content and build) is application code and was not separately tested; the pattern checks are what was verified.

Cost Estimate

• Currency: USD
• Monthly Amount: 5.0
• 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.0

Evidence Summary

• Canary Run
  Summary: Phoenix pattern fixture deployed on Ample... checks passed for versioned-static-assets and configuration-secrets. Pattern proof: ...
  Observed At: 2026-09-20T23:45:31Z
  Implementation Revision: 4d1511e574302f3904b75088bd4048a0975218b3-dirty (CLI 0.1.21)

Last Verified At

2026-09-20T23:45:31Z

Next Actions

1. Browse Catalog
   Action ID: browse-catalog
   Label: Browse the catalog index Method: GET
   Path: /v1/catalog Requires Authentication: No

2. Search Recipes
   Action ID: search-recipes
   Label: Search published recipes by intent, stack and constraints Method: POST
   Path: /v1/catalog/search Requires Authentication: No

3. Prepare Deployment Plan
   Action ID: plan:page:recipes:knowledge-base:phoenix:public-site
   Label: Prepare a side-effect-free deployment plan for an authorized project Method: POST
   Path: /v1/catalog/plan Requires Authentication: Yes

4. Read Existing Authentication Setup
   Action ID: auth-setup
   Label: Read the existing agent authentication setup Method: GET
   Path: /mcp/setup Requires Authentication: No

5. Browse Knowledge Base
   Action ID: browse:workload:knowledge-base
   Label: Browse Knowledge base Method: GET
   Path: /v1/catalog/nodes/workload%3Aknowledge-base Requires Authentication: No

6. Browse Phoenix
   Action ID: browse:stack:framework-phoenix
   Label: Browse Phoenix Method: GET
   Path: /v1/catalog/nodes/stack%3Aframework-phoenix Requires Authentication: No

7. Browse Public Web Service
   Action ID: browse:pattern:public-web-service
   Label: Browse Public web service Method: GET
   Path: /v1/catalog/nodes/pattern%3Apublic-web-service Requires Authentication: No

8. Browse Deploy Web App
   Action ID: browse:intent:deploy-web-app
   Label: Browse Deploy web app Method: GET
   Path: /v1/catalog/nodes/intent%3Adeploy-web-app Requires Authentication: No