# Host order tracking with Laravel: authorized file delivery

Deploy a order tracking 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 order tracking-specific behavior as your application code.

## Representative Queries
- Host order tracking with Laravel: authorized file delivery
- Where can I host Order tracking built with Laravel?
- I need a file entitlement model and an application-enforced download authorization flow.

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

## Framework and Workload
- **Framework**: Laravel
- **Workload**: Order tracking
- **Release Status**: published
- **Support Status**: verified
- **Execution Status**: ready

## 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 Command**: composer install --no-dev --prefer-dist --no-interaction --no-progress --optimize-autoloader  
- **Start Command**: frankenphp php-server --listen :$PORT --root public

## 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 generated downloads: 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). 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.
   Command: 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/generated-downloads) from the example; then run your own checks. On failure read `ample logs  --kind build` then `--kind runtime`.
   Command: ample logs  --kind build

## Success Checks
- App responds on its public URL (expected: ample canary laravel patterns)
- Generated-downloads self-test (expected: export=ok rows=3 (with ?token=...; 401 without))

## Limitations
- 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.
- The order tracking itself (your export formats, retention policy and entitlement model) 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  
- **Authoritative**: true
- **Basis**: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
  - **Components**:
    - App server - s-1vcpu-1gb - 1.0 - $5.0
    - Managed PostgreSQL database - s-1vcpu-1gb - 1.0 - $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.

## Next Actions
1. **Browse the catalog index**: GET /v1/catalog
2. **Search published recipes by intent, stack and constraints**: POST /v1/catalog/search
   Query: {"limit":5,"query":"Host order tracking with Laravel: authorized file delivery"}
3. **Prepare a side-effect-free deployment plan for an authorized project**: POST /v1/catalog/plan
4. **Read the existing agent authentication setup**: GET /mcp/setup
5. **Browse Order tracking**: GET /v1/catalog/nodes/workload%3Aorder-tracking
6. **Browse Laravel**: GET /v1/catalog/nodes/stack%3Aframework-laravel
7. **Browse Generated downloads**: GET /v1/catalog/nodes/pattern%3Agenerated-downloads
8. **Browse Deploy web app**: GET /v1/catalog/nodes/intent%3Adeploy-web-app