Host csv import tool with Laravel: file attachments

Deploy a csv import tool built with Laravel on Ample using the browser file uploads 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: content-type and size validation that rejects disallowed files, an object written to a private bucket and a row linking the record to the object key (reject=ok upload=ok linked=ok). Not separately tested: your upload UI, allowed types, size limits and virus scanning; treat the csv import tool-specific behavior as your application code.

Representative Queries

• Host csv import tool with Laravel: file attachments
• Where can I host CSV import tool built with Laravel?
• I need a restricted upload flow, file validation and record-to-object linkage.

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

Laravel

Implementation 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 browser file uploads: content-type and size validation that rejects disallowed files, an object written to a private bucket and a row linking the record to the object key (reject=ok upload=ok linked=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.
5. Verify: Fetch the live URL and the pattern self-test route(s) (/p/browser-file-uploads) from the example; then run your own checks. On failure read ample logs --kind build then --kind runtime.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Components:
  • App server: 1 x s-1vcpu-1gb: $5.0
  • Managed PostgreSQL database: 1 x s-1vcpu-1gb: $5.0

Limitations

• Verified on the php-8.5 template at s-1vcpu-1gb. Other sizes, templates and Laravel major versions are not verified.
• The csv import tool itself (your upload UI, allowed types, size limits and virus scanning) is application code and was not separately tested; the pattern checks are what was verified.

Examples

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

Success Checks

1. App responds on its public URL: [GET /] - Expect: ample canary laravel patterns
2. Browser-file-uploads self-test: [GET /p/browser-file-uploads] - Expect: reject=ok upload=ok linked=ok

Next Actions

• Browse the catalog index: [GET /v1/catalog]
• Search published recipes by intent: [POST /v1/catalog/search]
• Prepare a side-effect-free deployment plan: [POST /v1/catalog/plan]