# Connect Postgres for Rails

Database connection for a Rails app on Ample. Verified on Rails: a managed PostgreSQL database auto-provisioned and injected as DATABASE_URL, with real queries succeeding at request time (records=ok). 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.

**Verified**  November 6, 2026

## What it runs on

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

- [Postgres verified](/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.

## You need

- A Rails project (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
- An Ample account token with servers:write, databases:read

## Exact tested configuration

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

runtime ruby

sizes-1vcpu-1gb

start bundle exec rails server -b 0.0.0.0 -p $PORT

template 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. **Read DATABASE_URL at runtime.** Open connections from the environment inside handlers or a pool; omit DATABASE_URL to auto-provision a managed database or pass --env DATABASE_URL=... for an existing one.

3. **Verify.** Fetch the live URL and /p/relational-records on the example; on failure read the build and runtime logs.

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

## How it was checked

✓ app responds on its public URL · http get/ → “ample canary rails patterns”  
✓ relational-records check from the example · http get/p/relational-records → “see the pattern fixture checks”

## 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); for this guide: a managed PostgreSQL database auto-provisioned and injected as DATABASE_URL, with real queries succeeding at request time (records=ok).

## Tested examples

- **Rails pattern fixture.** Verified database connection on Rails.

## What it doesn’t cover

- Verified on the ruby-3.4 template at s-1vcpu-1gb.
- Managed PostgreSQL 16 with pgvector.
