Host project tracker with Rails: relational workspace data

Deploy a project tracker built with Rails on Ample using the relational records 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. Verified on Rails: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true).

Summary

Not separately tested: your record schema, states and access rules; treat the project tracker-specific behavior as your application code.

Representative Queries

• Host project tracker with Rails: relational workspace data
• Where can I host Project tracker built with Rails?
• I need a workspace-specific schema, state transitions and access rules.

Resource Requirements

• primitive:compute
• primitive:postgres

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. (Verified)
• 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. (Verified)

Prerequisites

1. 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).
2. A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env).
3. An Ample account token with servers:write, databases:read.

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 relational records: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true). Copy the approach into your schema; keep migrations idempotent and run them with --release-command.
3. 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. ample deploy . --name --public
4. Verify: Fetch the live URL and the pattern self-test route(s) (/p/relational-records) from the example; then run your own checks. On failure read ample logs --kind build then --kind runtime. ample logs --kind build

Success Checks

• App responds on its public URL (HTTP GET /, expect ample canary rails patterns).
• Relational-records self-test (HTTP GET /p/relational-records, expect records=ok transitions=true isolation=true).

Limitations

• Verified on the ruby-3.4 template at s-1vcpu-1gb with the example fixture; other sizes, templates and Rails major versions are not verified.
• The project tracker itself (your record schema, states and access 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.
• 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.

Cost Estimate

• Monthly Amount: $10.00 (USD)
• Basis: Size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
• Components:
  • App server: 1 x s-1vcpu-1gb = $5.00
  • Managed PostgreSQL database: 1 x s-1vcpu-1gb = $5.00

Evidence Summary

1. Canary Run: Rails pattern fixture deployed on Ample; checks passed for relational-records and configuration-secrets.

   • Observed at: 2026-09-20T21:55:28Z
   • Implementation Revision: 4f7cb9813c1f-dirty (CLI 4f7cb98)
   • Expires at: 2027-03-19T21:55:28Z

2. Canary Run: The same Rails app deployed with a --release-command migration.

   • Observed at: 2026-09-20T21:55:28Z
   • Expires at: 2027-03-19T21:55:28Z

Last Verified At

• 2026-09-20T21:55:28Z

Formats

• HTML: https://ample.computer/recipes/project-tracker/rails/relational-workspace
• Markdown: https://ample.computer/recipes/project-tracker/rails/relational-workspace.md
• JSON: https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Aproject-tracker%3Arails%3Arelational-workspace