page:recipes:vendor portal:laravel:activity history

Host vendor portal with Laravel: application activity history

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

Representative Queries

Resource Requirements

Infrastructure Requirements

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

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 transactional workflows: 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). 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/transactional-workflows) from the example; then run your own checks. On failure read ample logs --kind build then --kind runtime. Command: ample logs --kind build.

Limitations

Cost Estimate

Evidence Summary

Next Actions

  1. Browse the catalog index: Method: GET, Relative Path: /v1/catalog
  2. Search published recipes by intent, stack, and constraints: Method: POST, Relative Path: /v1/catalog/search
  3. Prepare a side-effect-free deployment plan for an authorized project: Method: POST, Relative Path: /v1/catalog/plan
  4. Read the existing agent authentication setup: Method: GET, Relative Path: /mcp/setup
  5. Browse Vendor portal: Method: GET, Relative Path: /v1/catalog/nodes/workload%3Avendor-portal
  6. Browse Laravel: Method: GET, Relative Path: /v1/catalog/nodes/stack%3Aframework-laravel