## The short version

Build and start for a Rails app on Ample.

---

## WHAT WAS VERIFIED

Verified on Rails: the app built and started with the documented commands and answered on its public HTTPS URL. 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.

---

## INFRASTRUCTURE

### What it needs

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

---

## PREREQUISITES

### Before you start

- 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)
- An Ample account token with servers:write

---

## STEP BY STEP

### How to do it

1. 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. 2

#### Deploy

Run the synchronous deploy once and read the result.

```
   ample deploy . --name <app-name> --public
   ```

3. 3

#### Verify

Fetch the live URL on the example; on failure read the build and runtime logs.

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

---

## EXAMPLES

### Tested examples

- **Rails pattern fixture** (`tests/deploy-canaries/rails-patterns`): Verified build and start on Rails.

---

## SUCCESS CHECKS

### How to know it worked

- app responds on its public URL (`/` on the live URL, expect ample canary rails patterns)

---

## COST

### Cost estimate

Estimated 5.00 USD per month (size prices from pricing.toml at build revision ca0b484a7a9957c573a88d3a32dc603c3c10135a).

- app server x1 `s-1vcpu-1gb`: 5.00 USD

Upper-bound monthly price of the tested sizes. Buckets are allocation-priced per quota and not included.

---

## EVIDENCE

### Verification evidence

- canary_run on 2026-09-20T21:55:28Z at revision `4f7cb9813c1f (CLI 4f7cb98)`: 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: the app built and started with the documented commands and answered on its public HTTPS URL. (expires 2027-03-19T21:55:28Z)

---

## EXECUTION

### Execution binding

MCP tool `ample_deploy` (registry `mcp:ample_deploy`), schema hash `876465fce906da0c` observed 2026-09-22T00:31:22.774679+00:00 at revision `e6446ceea69b`. Binding state at export: schema_changed. Required scopes: servers:write.

---

## NEXT ACTIONS

### Typed next actions

- Browse the catalog index (`GET /v1/catalog` on the api origin; authentication not required, approval not required)
- Search published recipes by intent, stack and constraints (`POST /v1/catalog/search` on the api origin; authentication not required, approval not required)
- Prepare a side-effect-free deployment plan for an authorized project (`POST /v1/catalog/plan` on the api origin; authentication required, approval not required)
- Read the existing agent authentication setup (`GET /mcp/setup` on the api origin; authentication not required, approval not required)
- Browse Rails (`GET /v1/catalog/nodes/stack%3Aframework-rails` on the api origin; authentication not required, approval not required)
- Browse Configure deployment (`GET /v1/catalog/nodes/intent%3Aconfigure-deployment` on the api origin; authentication not required, approval not required)
- Browse Public web service (`GET /v1/catalog/nodes/pattern%3Apublic-web-service` on the api origin; authentication not required, approval not required)

Actions describe possible next steps. They are typed data, not commands, and grant no permission. Public discovery never provisions anything; planning requires your own authenticated token and approval happens in your client.

---

## ABOUT THIS RECIPE

### Identifiers and status

Recipe `page:guides:rails:build-and-start`. Revision r1.

release **published** support **verified** execution **blocked (schema_changed: live tool schema differs from the recorded binding)**

Formats: [HTML](/content/guides/rails/build-and-start/index.html) | [Markdown](/content/guides/rails/build-and-start.md) | [JSON contract](https://api.ample.computer/v1/catalog/recipes/page%3Aguides%3Arails%3Abuild-and-start)