page:recipes:storefront:laravel:relational catalog

Host storefront with Laravel: relational catalog data

Deploy a storefront built with Laravel on Ample using the transactional workflows 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: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected). Not separately tested: your domain records, validation rules and concurrency policy; treat the storefront-specific behavior as your application code.

Representative Queries

• Host storefront with Laravel: relational catalog data
• Where can I host Storefront built with Laravel?
• I need catalog tables, transactional update logic and application-level access boundaries.

Resource Requirements

• Compute
• Postgres

Infrastructure Requirements

1. Compute: 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: 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

• Laravel

Workload

• Storefront

Release Status

• Published

Support Status

• Verified

Execution Status

• Ready

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.

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: Copy the optimistic version check and event row checks 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/transactional-workflows) from the example; check accordingly.

Examples

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

Success Checks

1. App responds on its public URL: await response on /, expected ample canary laravel patterns.
2. Transactional-workflows self-test: check /p/transactional-workflows, expected tx=ok history=2 conflict=rejected.

Limitations

• Verified only on the php-8.5 template at s-1vcpu-1gb; other configurations are not verified.
• The storefront specifics (domain records, validation, concurrency policy) were not tested outside this setup.

Cost Estimate

• Currency: USD
• Monthly Amount: $10.00
• Components:
  • App server: s-1vcpu-1gb - $5.00
  • Managed PostgreSQL database: s-1vcpu-1gb - $5.00
• Note: Always-on monthly price; apps and databases auto-pause when idle.

Last Verified At

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

Evidence Summary

1. Canary run: Laravel pattern fixture deployed on Ample.
2. Canary run: Same Laravel app deployed with a --release-command migration; checks were passed.

Formats

• HTML
• Markdown
• JSON