page:recipes:crm:laravel:csv imports

Host CRM with Laravel: CSV Imports

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

Summary

Representative Queries

Resource Requirements

Infrastructure Requirements

  1. Compute

    • Status: verified
    • Summary: 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

    • Status: verified
    • Summary: 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

    • Status: verified
    • Summary: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

Prerequisites

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

Success Checks

Limitations

Cost Estimate

Evidence Summary

  1. Canary Run

    • Summary: Laravel pattern fixture deployed on Ample; checks passed for bulk-import-staging and configuration-secrets.
    • Observed At: 2026-09-20T20:36:21Z
  2. Canary Run

    • Summary: The same Laravel app deployed with a --release-command migration; the marker it created was readable after activation.
    • Observed At: 2026-09-20T20:36:21Z

Next Actions

  1. Browse the catalog index
    • Operation ID: catalog_index
    • Method: GET
    • Relative Path: /v1/catalog
  2. Search published recipes by intent, stack, and constraints
    • Operation ID: search_recipes
    • Method: POST
    • Relative Path: /v1/catalog/search
    • Parameters: { body: { limit: 5, query: "Host crm with Laravel: CSV imports" } }
  3. Prepare a side-effect-free deployment plan for an authorized project
    • Operation ID: plan_deployment
    • Method: POST
    • Relative Path: /v1/catalog/plan
  4. Read the existing agent authentication setup
    • Operation ID: existing_auth_setup
    • Method: GET
    • Relative Path: /mcp/setup
  5. Browse CRM
    • Operation ID: browse_node
    • Method: GET
    • Relative Path: /v1/catalog/nodes/workload%3Acrm
  6. Browse Laravel
    • Operation ID: browse_node
    • Method: GET
    • Relative Path: /v1/catalog/nodes/stack%3Aframework-laravel
  7. Browse Bulk import staging
    • Operation ID: browse_node
    • Method: GET
    • Relative Path: /v1/catalog/nodes/pattern%3Abulk-import-staging
  8. Browse Deploy web app
    • Operation ID: browse_node
    • Method: GET
    • Relative Path: /v1/catalog/nodes/intent%3Adeploy-web-app