# Host member portal with Phoenix: public profile assets

Deploy a member portal built with Phoenix on Ample using the public image delivery 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, and a published bucket serves public assets from the CDN host. Verified on Phoenix: public objects in a published bucket served from the CDN URL, kept separate from private objects in an unpublished bucket that require authorization (private=ok only for the allowed role). Not separately tested: your image processing and profile-media rules; treat the member portal-specific behavior as your application code.

## Representative Queries
- Host member portal with Phoenix: public profile assets
- Where can I host Member portal built with Phoenix?
- I need separate public profile media from private data, with CDN cache rules.

## Resource Requirements
- primitive:compute
- primitive:postgres
- primitive:s3-compatible-object-storage
- primitive:cdn

## Infrastructure Requirements
1. **Compute**  
   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**  
   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. **S3-compatible object storage**  
   Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.
4. **CDN**  
   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 public image delivery: public objects in a published bucket served from the CDN URL, kept separate from private objects in an unpublished bucket that require authorization (private=ok only for the allowed role). 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.
5. **Verify**  
   Fetch the live URL and the pattern self-test route(s) (/p/public-media-library, /p/private-document-library) from the example; then run your own checks. On failure read `ample logs --kind build` then `--kind runtime`.

## Success Checks
- **App responds on its public URL**
  - **Kind**: http_get  
  - **Path**: /  
  - **Expect**: ample canary phoenix patterns
- **Public-media-library self-test**  
  - **Kind**: http_get  
  - **Path**: /p/public-media-library  
  - **Expect**: a CDN URL whose content is served publicly
- **Private-document-library self-test**  
  - **Kind**: http_get  
  - **Path**: /p/private-document-library  
  - **Expect**: private=ok (with ?role=owner; 401 without, 403 for viewer)

## 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 member portal itself (your image processing and profile-media 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.

## Cost Estimate
- **Currency**: USD  
- **Monthly Amount**: 10.0  
- **Basis**: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
-  **Components**:  
   - **App server**: s-1vcpu-1gb, quantity: 1.0, monthlyAmount: 5.0
   - **Managed PostgreSQL database**: s-1vcpu-1gb, quantity: 1.0, monthlyAmount: 5.0

## Examples
1. **Phoenix pattern fixture**  
   Multi-pattern Phoenix app whose public image delivery module was checked live; the module is under tests/deploy-canaries/_pattern-modules.  
   **Source Reference**: tests/deploy-canaries/phoenix-patterns