Host reporting dashboard with Rails: file attachments · Ample Computer
Host Reporting Dashboard with Rails: File Attachments
Deploy a reporting dashboard 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). The reporting dashboard-specific behavior (your upload UI, allowed types, size limits and virus scanning) is your application code on that verified basis.
Verified: November 6, 2026
What It Runs On
Computeverified
Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.Postgresverified
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
Buckets speak the S3 API with SigV4 credentials Ample Computer issues;ample bucket upload-urlreturns 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 serverreading 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 createwith its credentials passed as encrypted S3_* environment variablesAn Ample account token with servers:write, databases:read, buckets:read
Exact Tested Configuration
installbundle config set --local path vendor/bundle && bundle config set --local without 'development test' && bundle install
runtimeruby
sizes-1vcpu-1gb
startbundle exec rails server -b 0.0.0.0 -p $PORT
templateruby-3.4
Steps
Build and Start. bundle install into vendor/bundle from Gemfile.lock (development and test groups skipped), then Puma via
rails serverreading PORT on the ruby-3.4 template with RAILS_ENV=production. The server must bind 0.0.0.0 on PORT.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.
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.
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.
$ 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/browser-file-uploads) from the example; then run your own checks. On failure read `ample logs <deployment_id> --kind build` then `--kind runtime`.
```bash
$ ample logs <deployment_id> --kind build
```
## How It Was Checked
✓ app responds on its public URL · http get/ → “ample canary rails patterns”
✓ browser-file-uploads self-test · http get/p/browser-file-uploads → “reject=ok upload=ok linked=ok”
## 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 browser-file-uploads and configuration-secrets. Pattern proof: 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).
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 browser file uploads 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 reporting dashboard itself (your upload UI, allowed types, size limits and virus scanning) 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.