page:recipes:crm:laravel:relational workspace

Host crm with Laravel: relational workspace data

Deploy a crm built with Laravel on Ample using the relational records 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. Verified on Laravel: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true). Not separately tested: your record schema, states and access rules; treat the crm-specific behavior as your application code.

Representative Queries

• Host crm with Laravel: relational workspace data
• Where can I host CRM built with Laravel?
• I need a workspace-specific schema, state transitions and access rules.

Resource Requirements

• primitive:compute
• primitive:postgres

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.

Framework

• Framework: Laravel
• Workload: CRM
• Release Status: Published
• Support Status: Verified
• Execution Status: Ready

Prerequisites

1. 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).
2. A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env).
3. An Ample account token with servers:write, databases:read.

Tested Configuration

• Template: php-8.5
• Runtime: php
• Size: s-1vcpu-1gb
• Install: composer install --no-dev --prefer-dist --no-interaction --no-progress --optimize-autoloader
• Start: frankenphp php-server --listen :$PORT --root public

Input Schema

• env: Encrypted environment variables (bucket credentials, secrets)
• name: App name
• path: Project directory or ample.toml service
• release_command: Migration command run before activation

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: Copy the approach into your schema; keep migrations idempotent and run them with --release-command.
3. Deploy: Run the synchronous deploy once and read the result (exit 0 live, 1 failed, 2 blocked).
4. Verify: Fetch the live URL and the pattern self-test route(s) (/p/relational-records) from the example; then run your own checks.

Examples

• Laravel pattern fixture: Multi-pattern Laravel app whose relational records module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

Success Checks

1. app responds on its public URL
2. relational-records self-test

Limitations

• Verified on the php-8.5 template; other sizes, templates and Laravel major versions are not verified.
• The crm itself (your record schema, states and access rules) is application code and was not separately tested.

Cost Estimate

• Monthly Amount: $10.0 (USD)
  • App server: $5.0
  • Managed PostgreSQL database: $5.0

Evidence Summary

• Canary Run: Laravel pattern fixture deployed on Ample; checks passed for relational-records and configuration-secrets.

Next Actions

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