Host CSV Import Tool with Laravel: Structured Data Imports

Deploy a CSV import tool 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 CSV import tool-specific behavior as your application code.

Representative Queries

• Host csv import tool with Laravel: structured data imports
• Where can I host CSV import tool built with Laravel?
• I need a workload-specific import mapping, conflict rules, and restart behavior.

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.
2. A PostgreSQL driver reading DATABASE_URL at runtime.
3. A bucket with its credentials passed as encrypted S3_* environment variables.
4. 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. 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. Re-running with no change is a no-op.
5. Verify: Fetch the live URL and the pattern self-test route(s) from the example; then run your own checks. On failure read logs.

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 CSV import tool itself is application code and was not separately tested.
• Region, compliance attestations, and request-duration limits are unknown and not claimed.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Components:
  • App server: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: 5.0
  • Managed PostgreSQL database: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: 5.0

Evidence Summary

1. Canary Run: Laravel pattern fixture deployed on Ample, checks passed for bulk-import-staging. Implementation revision noted.
2. Verified Commands: All commands have been executed and observed.

Exemplars

• Laravel Pattern Fixture: Multi-pattern Laravel app whose bulk import staging module was checked live.

Next Actions

• Browse Catalog: Explore the catalog index.
• Search Recipes: Search published recipes by intent, stack, and constraints.
• Prepare Deployment Plan: Prepare a side-effect-free deployment plan for an authorized project.
• Read Authentication Setup: Read the existing agent authentication setup.