page:recipes:recruiting tracker:laravel:relational workspace

Host recruiting tracker with Laravel: relational workspace data

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

Prerequisites

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

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

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

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, and a cross-workspace read that returns nothing (transitions=true isolation=true). 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). Re-running with no change is a no-op.
   • Command: ample deploy . --name --public
4. Verify: Fetch the live URL and the pattern self-test route(s) (/p/relational-records) from the example; then run your own checks. On failure read ample logs --kind build then --kind runtime.
   • Command: ample logs --kind build

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

• App responds on its public URL.
  • Check: http_get
  • Path: /
  • Expect: ample canary laravel patterns
• Relational-records self-test.
  • Check: http_get
  • Path: /p/relational-records
  • Expect: records=ok transitions=true isolation=true

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 recruiting tracker itself (your record schema, states and access rules) is application code and was not separately tested; the pattern checks are what was verified.
• Region, compliance attestations and request-duration limits are unknown and not claimed.
• Apps auto-pause when idle and wake on the next request; always-on is an operator setting, not a plan feature.
• Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified; apps and their databases are placed together.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Basis: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
• Components:
  • App server: size: s-1vcpu-1gb, quantity: 1.0, monthlyAmount: 5.0
  • Managed PostgreSQL database: size: s-1vcpu-1gb, quantity: 1.0, monthlyAmount: 5.0

Evidence Summary

1. Canary Run: Laravel pattern fixture deployed on Ample; checks passed for relational-records and configuration-secrets.
   • Observed At: 2026-09-20T20:36:21Z
2. Canary Run: 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

Last Verified At

• 2026-09-20T20:36:21Z

Formats

• HTML: HTML Link
• Markdown: Markdown Link
• JSON: JSON Link

Next Actions

• Browse the catalog index (GET /v1/catalog)
• Search published recipes by intent, stack and constraints (POST /v1/catalog/search)
• Prepare a side-effect-free deployment plan for an authorized project (POST /v1/catalog/plan)
• Read the existing agent authentication setup (GET /mcp/setup)
• Browse Recruiting tracker (GET /v1/catalog/nodes/workload%3Arecruiting-tracker)
• Browse Laravel (GET /v1/catalog/nodes/stack%3Aframework-laravel)
• Browse Relational records (GET /v1/catalog/nodes/pattern%3Arelational-records)
• Browse Deploy web app (GET /v1/catalog/nodes/intent%3Adeploy-web-app)