# Host public directory with Laravel: bulk content imports

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

## Representative Queries
- Host public directory with Laravel: bulk content imports  
- Where can I host Public directory built with Laravel?  
- I need a staged import format, validation procedure and import recovery workflow.

## 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.  
   ```bash  
   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`.  
   ```bash  
   ample logs  --kind build  
   ```

## Input Schema
```json
{
  "type": "object",
  "properties": {
    "env": {
      "description": "Encrypted environment variables (bucket credentials, secrets)",
      "type": "array",
      "items": {
        "type": "string",
        "pattern": "^[A-Z][A-Z0-9_]*=.*$"
      },
      "maxItems": 50
    },
    "name": {
      "description": "App name",
      "type": "string",
      "pattern": "^[a-z0-9-]+$",
      "minLength": 1,
      "maxLength": 63
    },
    "path": {
      "description": "Project directory or ample.toml service",
      "type": "string",
      "minLength": 1,
      "maxLength": 512
    },
    "release_command": {
      "description": "Migration command run before activation",
      "type": "string",
      "maxLength": 512
    }
  },
  "required": ["env", "name", "path"],
  "additionalProperties": false
}
```

## 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.  
   Source: `tests/deploy-canaries/laravel-patterns`.

## Success Checks
- App responds on its public URL  
  ```http
  GET /
  ```  
  Expect: `ample canary laravel patterns`
- Bulk-import-staging self-test  
  ```http
  GET /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 public directory 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  
- Basis: Size prices from pricing.toml (loaded by the API)  
  - App Server  
    - Size: s-1vcpu-1gb  
    - Quantity: 1.0  
    - Monthly Amount: 5.0  
  - Managed PostgreSQL Database  
    - Size: s-1vcpu-1gb  
    - Quantity: 1.0  
    - Monthly Amount: 5.0
- Note: Always-on monthly price of the tested sizes.
