page:recipes:blog:phoenix:relational content

Host blog with Phoenix: Postgres-backed content

Summary

Deploy a blog built with Phoenix on Ample using the relational records 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, and a published bucket serves public assets from the CDN host. Verified on Phoenix: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true). Not separately tested: your record schema, states and access rules; treat the blog-specific behavior as your application code.

Representative Queries

• Host blog with Phoenix: Postgres-backed content
• Where can I host Blog built with Phoenix?
• I need a content schema, publishing workflow and cache behavior after content updates.

Resource Requirements

• primitive:compute
• primitive:postgres
• primitive: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.

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.

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

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 relational records: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true). 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. Publish only the bucket that serves public assets and reference its CDN URL.
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.
   • Command: 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=...
5. Verify: Fetch the live URL and the pattern self-test route(s) (/p/relational-records) 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 relational records module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

Success Checks

1. HTTP GET on /: app responds on its public URL. Expect: ample canary phoenix patterns.
2. HTTP GET on /p/relational-records: relational-records self-test. Expect: records=ok transitions=true isolation=true.

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 blog itself (your record schema, states and access rules) 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.
• PutObject and GetObject with path-style addressing are verified; multipart upload, listing, presigned URLs and lifecycle rules are not.
• The CDN serves published-bucket objects only; cache rules, purge and TTL control are not verified.

Cost Estimate

• Monthly Amount: 10.0
• Currency: USD
• Components:
  • App server: 5.0 (size: s-1vcpu-1gb, quantity: 1.0)
  • Managed PostgreSQL database: 5.0 (size: s-1vcpu-1gb, quantity: 1.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

• Canary run: Phoenix pattern fixture deployed on Ample; checks passed for relational-records and configuration-secrets.
• Canary run: The same Phoenix app deployed with a --release-command migration; the marker it created was readable after activation.

Last Verified At

2026-09-20T23:45:31Z

Next Actions

• Browse the catalog: Catalog Index
• Search published recipes: Search published recipes
• Prepare a side-effect-free deployment plan: Prepare a deployment plan
• Read existing agent authentication setup: Existing auth setup
• Browse Blog: Browse Blog
• Browse Phoenix: Browse Phoenix
• Browse Relational records: Browse Relational records
• Browse Deploy web app: Browse Deploy web app