# Host partner portal with Laravel: application activity history

Deploy a partner 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`). The partner portal-specific behavior (your domain records, validation rules and concurrency policy) is your application code on that verified basis.

## What it runs on

- [Compute verified](/content/discover/primitive/compute/index.html)
  Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.

- [Postgres verified](/content/discover/primitive/postgres/index.html)
  Managed PostgreSQL 16 with pgvector runs in its own microVM and is auto-provisioned when an app needs a database and no `DATABASE_URL` is supplied.

## You need

- 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`

## Exact tested configuration

`install composer install --no-dev --prefer-dist --no-interaction --no-progress --optimize-autoloader`

`runtime php`

`sizes - 1vcpu-1gb`

`start frankenphp php-server --listen :$PORT --root public`

`template php-8.5`

## 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 needs an answer first). Re-running with no change is a no-op.

```
   $ ample deploy . --name <app-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 <deployment_id> --kind build` then `--kind runtime`.

```
   $ ample logs <deployment_id> --kind build
   ```

## How it was checked

✓ app responds on its public URL · `http get/` → “ample canary laravel patterns”  
✓ transactional-workflows self-test · `http get/p/transactional-workflows` → “tx=ok history=2 conflict=rejected”

## Evidence

1. November 6, 2026 · 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. Pattern proof: 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`).

2. November 6, 2026 · canary run
   
   The same Laravel app deployed with a `--release-command` migration; the marker it created was readable after activation.

## Tested examples

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

## What it doesn’t cover

- Verified on the `php-8.5` template at `s-1vcpu-1gb` with the example fixture.
- The pattern checks verified the platform side; the partner portal itself (your domain records, validation rules and concurrency policy) is your application code.
- Managed PostgreSQL 16 with pgvector; apps and their databases are placed together.
