page:recipes:member portal:laravel:activity history

Host member portal with Laravel: application activity history

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

Representative Queries

• Host member portal with Laravel: application activity history
• Where can I host Member portal built with Laravel?
• I need an application-owned event schema and tested history queries; not native platform audit logs.

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.
  Canonical Path: /discover/primitive/compute
• 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.
  Canonical Path: /discover/primitive/postgres

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

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.

   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.

   ample logs  --kind build
   

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

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 member portal itself (your domain records, validation rules and concurrency policy) 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
• Authoritative: true
• Basis: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty

Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.

Evidence Summary

• Canary Run: Laravel pattern fixture deployed on Ample (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); checks passed for transactional-workflows and configuration-secrets.
• Implementation Revision: 118ad1c6d7d23d4c2ce069254bab9ec9d37cd57b-dirty (CLI 118ad1c)
• Observed At: 2026-09-20T20:36:21Z

Next Actions

• Browse the catalog index
  Action ID: browse-catalog
• Search published recipes by intent, stack, and constraints
  Action ID: search-recipes
• Prepare a side-effect-free deployment plan for an authorized project
  Action ID: plan:page:recipes:member-portal:laravel:activity-history
• Read the existing agent authentication setup
  Action ID: auth-setup
• Browse Member portal
  Action ID: browse:workload:member-portal
• Browse Laravel
  Action ID: browse:stack:framework-laravel
• Browse Transactional workflows
  Action ID: browse:pattern:transactional-workflows
• Browse Deploy web app
  Action ID: browse:intent:deploy-web-app

This document outlines the process of hosting a member portal with Laravel, detailing the required resources, workflow steps, and testing configurations.