# Host event registration with Rails: data exports

Deploy an event registration built with Rails on Ample using the generated downloads 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: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3). The event registration-specific behavior (your export formats, retention policy and entitlement model) is your application code on that verified basis.

## What it runs on

- [Computeverified](/content/discover/primitive/compute/index.html)  
  Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.

- [Postgresverified](/content/discover/primitive/postgres/index.html)  
  Managed PostgreSQL 16 with pgvector runs in its own microVM and is auto-provisioned when an app needs a database and no `DATABASE_URL` is supplied.

- [S3-compatible object storageverified](/content/discover/primitive/s3-compatible-object-storage/index.html)  
  Buckets speak the S3 API with SigV4 credentials Ample Computer issues; `ample bucket upload-url` returns a presigned upload URL. PutObject and GetObject are checked by canary.

## You need

- 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

## Exact tested configuration

install

```sh
bundle config set --local path vendor/bundle && bundle config set --local without 'development test' && bundle install
```

runtime

```sh
ruby
```

sizes-1vcpu-1gb

start

```sh
bundle exec rails server -b 0.0.0.0 -p $PORT
```

template

```sh
ruby-3.4
```

## 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 generated downloads: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3). 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 needs an answer first). Re-running with no change is a no-op.

```sh
$ ample deploy . --name <app-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/generated-downloads) from the example; then run your own checks. On failure read `ample logs <deployment_id> --kind build` then `--kind runtime`.

```sh
$ ample logs <deployment_id> --kind build
```

## How it was checked

✓ app responds on its public URL· http get/ → "ample canary rails patterns"

✓ generated-downloads self-test· http get/p/generated-downloads → "export=ok rows=3 (with ?token=...; 401 without)"

## Evidence

1. November 6, 2026 · canary run  
   Rails pattern fixture deployed on Ample (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`); checks passed for generated-downloads and configuration-secrets. Pattern proof: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3).

2. November 5, 2026 · canary run  
   The same Rails app deployed with a --release-command migration; the marker it created was readable after activation.

## Tested examples

- **Rails pattern fixture.** Multi-pattern Rails app whose generated downloads module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

## What it doesn’t cover

- Verified on the ruby-3.4 template at s-1vcpu-1gb with the example fixture.

- The pattern checks verified the platform side; the event registration itself (your export formats, retention policy and entitlement model) is your application code.

- Managed PostgreSQL 16 with pgvector; apps and their databases are placed together.

- Buckets speak the standard S3 API (PutObject and GetObject with path-style addressing are checked by the fixture); `ample bucket upload-url` returns presigned upload URLs.
