page:recipes:approval workflow:laravel:relational workspace

Host Approval Workflow with Laravel: Relational Workspace Data

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

Summary

• Framework: Laravel
• Workload: Approval workflow
• Release Status: Published
• Support Status: Verified
• Execution Status: Ready
• Docs Only: False

Representative Queries

1. Host approval workflow with Laravel: relational workspace data
2. Where can I host Approval workflow built with Laravel?
3. I need a workspace-specific schema, state transitions, and access rules.

Resource Requirements

• Primitive Compute
• Primitive Postgres

Infrastructure Requirements

• 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.
• 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.

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 Command: composer install --no-dev --prefer-dist --no-interaction --no-progress --optimize-autoloader
• Start Command: frankenphp php-server --listen :$PORT --root public

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 relational records: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions. 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.

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 record schema, states, and access rules) is application code and was not separately tested; the pattern checks are what was verified.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

Evidence Summary

1. Canary Run
   • Laravel pattern fixture deployed on Ample, checks passed for relational-records and configuration-secrets.
2. Canary Run
   • The same Laravel app deployed with a --release-command migration; the marker it created was readable after activation.

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 Relational records
8. Browse Deploy web app

For more details, you can access the following formats:

• HTML Format
• Markdown Format
• JSON Format