page:recipes:approval workflow:laravel:csv imports

Host approval workflow with Laravel: CSV imports

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

Representative Queries

• Host approval workflow with Laravel: CSV imports
• Where can I host Approval workflow built with Laravel?
• I need a domain CSV format, row validation, deduplication and an import recovery path.

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

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

Success Checks

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

Cost Estimate

• Currency: USD
• Monthly Amount: $10.00
• Components:
  • Name: app server, Size: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: $5.00
  • Name: managed PostgreSQL database, Size: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: $5.00
• 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.

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 approval workflow itself (your import format, mapping and conflict rules) is application code and was not separately tested; the pattern checks are what was verified.
• Apps auto-pause when idle and wake on the next request; always-on is an operator setting, not a plan feature.

Next Actions

1. Browse the catalog index
2. Search published recipes by intent, stack and constraints
3. Prepare a side-effect-free deployment plan for an authorized project
4. Read the existing agent authentication setup
5. Browse Approval workflow
6. Browse Laravel
7. Browse Bulk import staging
8. Browse Deploy web app

Examples

• Title: Laravel pattern fixture Description: Multi-pattern Laravel app whose bulk import staging module was checked live; the module is under tests/deploy-canaries/_pattern-modules. Source Ref: tests/deploy-canaries/laravel-patterns