## Host client portal with Laravel: private documents

Deploy a client portal built with Laravel on Ample using the private document library 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: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok). Not separately tested: your identity integration and role assignments; treat the client portal-specific behavior as your application code.

### Representative Queries
- Host client portal with Laravel: private documents
- Where can I host Client portal built with Laravel?
- I need a role-to-document access model and negative authorization tests.

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

### Workflow Steps
1. **Build and start**  
   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. The server must bind 0.0.0.0 on PORT.
2. **Implement the pattern on PostgreSQL**  
   The fixture's module implements private document library: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=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.
   ```bash
   ample deploy . --name <APP_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/private-document-library) from the example; then run your own checks. On failure read `ample logs  --kind build` then `--kind runtime`.
   ```bash
   ample logs  --kind build
   ```

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

### Examples
- **Laravel pattern fixture**: Multi-pattern Laravel app whose private document library module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

### Cost Estimate
- **Monthly Amount**: 10.0 USD  
   - **Components**:  
     - App server: s-1vcpu-1gb - 5.0 USD  
     - Managed PostgreSQL database: s-1vcpu-1gb - 5.0 USD  
   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.