# Host appointment booking with Rails: file attachments

Deploy a appointment booking built with Rails 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 Rails: 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 Rails: file attachments
- Where can I host Appointment booking built with Rails?
- 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
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.

## Prerequisites
- A Rails project that builds and starts with the documented commands (bundle install into vendor/bundle from Gemfile.lock (development and test groups skipped), then Puma via `rails server` reading PORT on the ruby-3.4 template with RAILS_ENV=production).
- A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env).
- A bucket from `ample bucket create` with its credentials passed as encrypted S3_* environment variables.
- An Ample account token with servers:write, databases:read, buckets:read.

## Tested Configuration
- **Template**: ruby-3.4
- **Runtime**: ruby
- **Size**: s-1vcpu-1gb
- **Install**: bundle config set --local path vendor/bundle && bundle config set --local without 'development test' && bundle install
- **Start**: bundle exec rails server -b 0.0.0.0 -p $PORT

## Workflow Steps
1. **Build and start**: bundle install into vendor/bundle from Gemfile.lock (development and test groups skipped), then Puma via `rails server` reading PORT on the ruby-3.4 template with RAILS_ENV=production. 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.
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`.

## Next Actions
- **Browse the catalog index**: method: GET, relative path: /v1/catalog
- **Search published recipes by intent, stack and constraints**: method: POST, relative path: /v1/catalog/search
- **Prepare a side-effect-free deployment plan for an authorized project**: method: POST, relative path: /v1/catalog/plan
- **Read the existing agent authentication setup**: method: GET, relative path: /mcp/setup
- **Browse Appointment booking**: method: GET, relative path: /v1/catalog/nodes/workload%3Aappointment-booking
- **Browse Rails**: method: GET, relative path: /v1/catalog/nodes/stack%3Aframework-rails
- **Browse Browser file uploads**: method: GET, relative path: /v1/catalog/nodes/pattern%3Abrowser-file-uploads
- **Browse Deploy web app**: method: GET, relative path: /v1/catalog/nodes/intent%3Adeploy-web-app