# Host appointment booking with Phoenix: File Attachments

## Summary
Deploy an appointment booking built with Phoenix on Ample using the browser file uploads 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. Verified on Phoenix: content-type and size validation that rejects disallowed files, an object written to a private bucket and a row linking the record to the object key (reject=ok upload=ok linked=ok). Not separately tested: your upload UI, allowed types, size limits, and virus scanning; treat the appointment booking-specific behavior as your application code.

## Representative Queries
- Host appointment booking with Phoenix: file attachments
- Where can I host Appointment booking built with Phoenix?
- I need a restricted upload flow, file validation, and record-to-object linkage.

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

## Infrastructure Requirements
- **Compute**: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
- **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.
- **S3-compatible object storage**: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

## Prerequisites
1. 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).
2. A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env).
3. A bucket from `ample bucket create` with its credentials passed as encrypted S3_* environment variables.
4. An Ample account token with servers:write, databases:read, buckets: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 browser file uploads: content-type and size validation that rejects disallowed files, an object written to a private bucket and a row linking the record to the object key (reject=ok upload=ok linked=ok). 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.
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=...
5. **Verify**: Fetch the live URL and the pattern self-test route(s) (/p/browser-file-uploads) from the example; then run your own checks. On failure read `ample logs --kind build` then `--kind runtime`.
   - Command: ample logs --kind build

## 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 appointment booking itself (your upload UI, allowed types, size limits, and virus scanning) 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.
- PutObject and GetObject with path-style addressing are verified; multipart upload, listing, presigned URLs, and lifecycle rules are not verified.

## 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, monthly amount: 5.0)
  - **Managed PostgreSQL database**: 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.

## Success Checks
- **App responds on its public URL**: (kind: http_get, path: /, expect: ample canary phoenix patterns)
- **Browser-file-uploads self-test**: (kind: http_get, path: /p/browser-file-uploads, expect: reject=ok upload=ok linked=ok)

## Evidence Summary
- Summary of canary runs noting implementation details and checks completed across specific timestamps.

## Next Actions
- **Browse the catalog index**: (actionId: browse-catalog, method: GET)
- **Search published recipes**: (actionId: search-recipes, method: POST)
- **Prepare a deployment plan**: (actionId: plan:page:recipes:appointment-booking:phoenix:attachments, method: POST)
- **Read existing authentication setup**: (actionId: auth-setup, method: GET)
- **Browse Appointment booking**: (actionId: browse:workload:appointment-booking, method: GET)
- **Browse Phoenix**: (actionId: browse:stack:framework-phoenix, method: GET)
- **Browse Browser file uploads**: (actionId: browse:pattern:browser-file-uploads, method: GET)
- **Browse Deploy web app**: (actionId: browse:intent:deploy-web-app, method: GET)