## Host order tracking with Laravel: inventory imports

Deploy an order tracking built with Laravel 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 Laravel: 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 order tracking-specific behavior as your application code.

### Representative Queries
- Host order tracking with Laravel: inventory imports
- Where can I host Order tracking built with Laravel?
- I need an inventory import contract, staging objects and row-level error handling.

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

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

### Success Checks
- **App responds on its public URL**: `http_get` path: `/`, expect: `ample canary laravel patterns`
- **Bulk-import-staging self-test**: `http_get` path: `/p/bulk-import-staging`, expect: `imported=2 rejected=1 restart=ok`

### 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 import format, mapping and conflict rules) is application code and was not separately tested; the pattern checks are what was verified.

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