# Host partner portal with Laravel: public profile assets

Deploy a partner portal built with Laravel on Ample using the public image delivery 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, and a published bucket serves public assets from the CDN host. Verified on Laravel: public objects in a published bucket served from the CDN URL, kept separate from private objects in an unpublished bucket that require authorization (private=ok only for the allowed role). Not separately tested: your image processing and profile-media rules; treat the partner portal-specific behavior as your application code.

## Representative Queries
- Host partner portal with Laravel: public profile assets
- Where can I host Partner portal built with Laravel?
- I need separate public profile media from private data, with CDN cache rules.

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

## Infrastructure Requirements
### Compute
- **Status:** verified  
- **Summary:** Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.

### Postgres
- **Status:** verified  
- **Summary:** 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
- **Status:** verified  
- **Summary:** Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

### CDN
- **Status:** verified  
- **Summary:** The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store.

## Prerequisites
1. 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)
2. A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env)
3. A bucket from `ample bucket create` with its credentials passed as encrypted S3_* environment variables and a second, published bucket for public assets (CDN_*)
4. An Ample account token with servers:write, databases:read, buckets:read

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

### Implement the pattern on PostgreSQL
- The fixture's module implements public image delivery: public objects in a published bucket served from the CDN URL, kept separate from private objects in an unpublished bucket that require authorization (private=ok only for the allowed role). Copy the approach into your schema; keep migrations idempotent and run them with --release-command.

### 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. Publish only the bucket that serves public assets and reference its CDN URL.

### 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  --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=... --env CDN_PUBLIC_URL=...
  ```

### Verify
- Fetch the live URL and the pattern self-test route(s) (/p/public-media-library, /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
  ```

## Success Checks
- App responds on its public URL
- Public-media-library self-test
- Private-document-library self-test

## Limitations
1. Verified on the php-8.5 template at s-1vcpu-1gb with the example fixture; other sizes, templates and Laravel major versions are not verified.
2. The partner portal itself (your image processing and profile-media rules) is application code and was not separately tested;
3. Apps auto-pause when idle and wake on the next request; always-on is an operator setting, not a plan feature.

## Cost Estimate
- **Estimated Monthly Amount:** $10.00 (USD)
- **Basis:** size prices from pricing.toml (loaded by the API)
- **Components:**  
  - App server: 1 x $5.00  
  - Managed PostgreSQL database: 1 x $5.00

## Evidence Summary
- **Canary Run:** Laravel pattern fixture deployed on Ample; checks passed for public-media-library and private-document-library.

## Formats
- **HTML:** [View on Ample](/content/recipes/partner-portal/laravel/public-profiles/index.html)
- **Markdown:** [Markdown version](/content/recipes/partner-portal/laravel/public-profiles.md) 
- **JSON:** [JSON Data](https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Apartner-portal%3Alaravel%3Apublic-profiles)
