# Host marketplace with Laravel: inventory imports

Deploy a marketplace 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). The marketplace-specific behavior (your import format, mapping and conflict rules) is your application code on that verified basis.

Verified on November 6, 2026

## What it runs on

- [Computeverified](/content/discover/primitive/compute/index.html)  
  Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.

- [Postgresverified](/content/discover/primitive/postgres/index.html)  
  Managed PostgreSQL 16 with pgvector runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

- [S3-compatible object storageverified](/content/discover/primitive/s3-compatible-object-storage/index.html)  
  Buckets speak the S3 API with SigV4 credentials Ample Computer issues; \`ample bucket upload-url\` returns a presigned upload URL. PutObject and GetObject are checked by canary.

## You need

- 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

## Exact tested configuration

install  
composer install --no-dev --prefer-dist --no-interaction --no-progress --optimize-autoloader

runtime  
php

sizes  
1vcpu-1gb

start  
frankenphp php-server --listen :$PORT --root public

template  
php-8.5

## 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 needs an answer first). Re-running with no change is a no-op.

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

```
    $ ample logs <deployment_id> --kind build
    ```

## How it was checked

✓ app responds on its public URL · http get/ → “ample canary laravel patterns”  
✓ bulk-import-staging self-test · http get/p/bulk-import-staging → “imported=2 rejected=1 restart=ok”

## Evidence

1. November 6, 2026 · canary run  
   Laravel pattern fixture deployed on Ample (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); checks passed for bulk-import-staging and configuration-secrets. Pattern proof: 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).

2. November 6, 2026 · canary run  
   The same Laravel app deployed with a --release-command migration; the marker it created was readable after activation.

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

## What it doesn’t cover

- Verified on the php-8.5 template at s-1vcpu-1gb with the example fixture.
- The pattern checks verified the platform side; the marketplace itself (your import format, mapping and conflict rules) is your application code.
- Managed PostgreSQL 16 with pgvector; apps and their databases are placed together.
- Buckets speak the standard S3 API (PutObject and GetObject with path-style addressing are checked by the fixture); \`ample bucket upload-url\` returns presigned upload URLs.
