## Host form collection with Laravel: data exports

Deploy a form collection built with Laravel on Ample using the generated downloads 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 Laravel: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3). Not separately tested: your export formats, retention policy and entitlement model; treat the form collection-specific behavior as your application code.

### Representative Queries
- Host form collection with Laravel: data exports
- Where can I host Form collection built with Laravel?
- I need a scoped export format, artifact generation and authorized download procedure.

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

### Infrastructure Requirements
1. **Compute**  
   Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
2. **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.
3. **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 Laravel project that builds and starts with the documented commands (composer install --no-dev from composer.lock, then FrankenPHP serving public/ (php-server with the index.php fallback) reading PORT on the php-8.5 template)
- 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

### Tested Configuration
- **Template**: php-8.5  
- **Runtime**: php  
- **Size**: s-1vcpu-1gb
- **Install**: composer install --no-dev --prefer-dist --no-interaction --no-progress --optimize-autoloader
- **Start**: frankenphp php-server --listen :$PORT --root public

### Workflow Steps
1. **Build and start**  
   compose install --no-dev from composer.lock, then FrankenPHP serving public/.
2. **Implement the pattern on PostgreSQL**  
   The fixture's module implements generated downloads: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller.
3. **Wire object storage**  
   Create the bucket(s), then pass endpoint, region, bucket and keys as --env values.
4. **Deploy**  
   Run the synchronous deploy once and read the result (exit 0 live, 1 failed, 2 blocked).
5. **Verify**  
   Fetch the live URL and the pattern self-test route(s);

### Success Checks
- app responds on its public URL
- generated-downloads self-test

### Limitations
- Verified on the php-8.5 template at s-1vcpu-1gb with the example fixture.
- The form collection itself is application code and was not separately tested; the pattern checks are what was verified.
- Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified.

### Cost Estimate
- **Monthly Amount**: 10.0 USD  
- Basis: size prices from pricing.toml at build revision. 
- Components:  
   - app server: s-1vcpu-1gb, quantity: 1.0, monthly amount: 5.0  
   - managed PostgreSQL database: s-1vcpu-1gb, quantity: 1.0, monthly amount: 5.0

### Next Actions
- **Browse the catalog index**  
   - Method: GET
- **Search published recipes by intent**  
   - Method: POST
   
- **Plan a deployment**  
   - Method: POST  
   
- **Read existing agent authentication setup**  
   - Method: GET

### Evidence Summary
- **Canary Run**: Laravel pattern fixture deployed on Ample; checks passed for generated-downloads and configuration-secrets.
- **Canary Run**: Laravel app deployed with a --release-command migration; the marker it created was readable after activation.