# Host asset library with Rails: structured data imports

Deploy an asset library built with Rails on Ample using the bulk import staging 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: a CSV staged as an object, row-level validation with per-row errors recorded, and a restart-safe import keyed by import id (imported=2 rejected=1 restart=ok). Not separately tested: your import format, mapping and conflict rules; treat the asset library-specific behavior as your application code.

## Representative Queries
* Host asset library with Rails: structured data imports
* Where can I host Asset library built with Rails?
* I need a workload-specific import mapping, conflict rules and restart behavior.

## Resource Requirements
* primitive:compute
* primitive:postgres
* primitive:s3-compatible-object-storage

## 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.

### 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.

### S3-compatible object storage
Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

## Prerequisites
* 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

## 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 bulk import staging: a CSV staged as an object, row-level validation with per-row errors recorded, and a restart-safe import keyed by import id (imported=2 rejected=1 restart=ok). 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 blocked). Re-running with no change is a no-op.  
`ample deploy . --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/bulk-import-staging) 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` – Path: `/` – Expect: `ample canary rails patterns`
* **Bulk-import-staging self-test**  
`http_get` – Path: `/p/bulk-import-staging` – Expect: `imported=2 rejected=1 restart=ok`

## 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 asset library itself (your import format, mapping and conflict 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.
* PutObject and GetObject with path-style addressing are verified; multipart upload, listing, presigned URLs and lifecycle rules are not verified.

## Cost Estimate
Currency: USD  
Monthly Amount: 10.0

### Components
* App server s-1vcpu-1gb: 5.0
* Managed PostgreSQL database s-1vcpu-1gb: 5.0

Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.

## Evidence Summary
* **Canary Run**  
Rails pattern fixture deployed on Ample; checks passed for bulk-import-staging and configuration-secrets. Pattern proof: a CSV staged as an object, row-level validation with per-row errors recorded, and a restart-safe import keyed by import id (imported=2 rejected=1 restart=ok).

## Next Actions
1. **Browse the catalog index**
2. **Search published recipes by intent, stack and constraints**
3. **Prepare a side-effect-free deployment plan for an authorized project**
4. **Read the existing agent authentication setup**
5. **Browse Asset library**
6. **Browse Rails**
7. **Browse Bulk import staging**
8. **Browse Deploy web app**