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
- Host vendor portal with Laravel: application activity history
- Where can I host Vendor portal built with Laravel?
- I need an application-owned event schema and tested history queries; not native platform audit logs.
Resource Requirements
- Compute
- 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.
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
- 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.
- 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.
- 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.
- 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 buildthen--kind runtime. Command: ample logs --kind build.
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 vendor portal itself (your domain records, validation rules and concurrency policy) is application code and was not separately tested.
- 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.
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 (s-1vcpu-1gb) : $5.00/month
- managed PostgreSQL database (s-1vcpu-1gb) : $5.00/month
- Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.
Evidence Summary
- Kind: canary_run
- Summary: Laravel pattern fixture deployed on Ample . . checks passed for transactional-workflows and configuration-secrets.
- Observed At: 2026-09-20T20:36:21Z
- Implementation Revision: 118ad1c6d7d23d4c2ce069254bab9ec9d37cd57b-dirty
Next Actions
- Browse the catalog index: Method: GET, Relative Path: /v1/catalog
- Search published recipes by intent, stack, and constraints: Method: POST, Relative Path: /v1/catalog/search
- Prepare a side-effect-free deployment plan for an authorized project: Method: POST, Relative Path: /v1/catalog/plan
- Read the existing agent authentication setup: Method: GET, Relative Path: /mcp/setup
- Browse Vendor portal: Method: GET, Relative Path: /v1/catalog/nodes/workload%3Avendor-portal
- Browse Laravel: Method: GET, Relative Path: /v1/catalog/nodes/stack%3Aframework-laravel