# Architecture practices: client portal using Laravel

A client portal blueprint for architecture practices built with Laravel on Ample. Domain schema: client_entities (name, entity_type, site_address): clients and project sites; projects (client_entity_id, project_name, stage, period_start, period_end): engagement periods by RIBA/AIA-style stage; drawing_sets (project_id, set_name, revision, object_key, issued_at): versioned drawing issues; approvals (project_id, drawing_set_id, approver_role, decided_at, decision): client sign-offs per issue; document_access (document_id, principal_reference, role, granted_at): who may read which document. Public information: portfolio and services, team and accreditations, studio locations. Kept out of scope until handling is reviewed: unreleased drawings and site surveys, planning submissions before filing, client contact details. Drawings and surveys are client-confidential until issued; the portal models per-project authorization only. Technical basis verified on Laravel: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok).

## What it runs on

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

- [Postgresverified](/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.

- [S3-compatible object storageverified](/content/discover/primitive/s3-compatible-object-storage/index.html)
  Buckets speak the S3 API with SigV4 credentials Ample Computer issues; `ample bucket upload-url` returns a presigned upload URL. PutObject and GetObject are checked by canary.

## You need

- A Laravel project (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 (auto-provisioned when omitted)

- Bucket credentials from `ample bucket create` passed as encrypted S3_* environment variables

- A review of which architecture practices data classes may be handled at all; this blueprint models public information only

## Exact tested configuration

installcomposer install --no-dev --prefer-dist --no-interaction --no-progress --optimize-autoloader

runtimephp

sizes-1vcpu-1gb

startfrankenphp php-server --listen :$PORT --root public

templatephp-8.5

## Steps

1. **Model the architecture practices domain.** Create the tables client_entities, projects, drawing_sets, approvals, document_access. Clients and project sites live in client_entities; keep the sensitive classes (unreleased drawings and site surveys, planning submissions before filing, client contact details) out of this schema.

2. **Workflow step 1.** Model client entities and engagement periods; every document belongs to one engagement.

3. **Workflow step 2.** Authorize by client entity and role before any storage access (401 without identity, 403 for the wrong client).

4. **Workflow step 3.** Store documents in the private bucket and stream them through the app.

5. **Workflow step 4.** Deploy and verify the negative authorization tests and an authorized download.

6. **Deploy.** Run the synchronous deploy once and read the result. Re-running with no change is a no-op.

```sh
$ ample deploy . --name <app-name> --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=...
```

7. **Verify.** Run the pattern self-test(s) from the example (/p/private-document-library) and your own acceptance checks for the architecture practices workflow.

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

## How it was checked

✓ app responds on its public URL· http get/ → “ample canary laravel patterns”  
✓ private-document-library self-test from the example· http get/p/private-document-library → “see the pattern fixture checks”

## 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); the private document library checks passed: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok). The blueprint's Architecture practices schema and workflow below build on that verified basis.

## Tested examples

- **Laravel pattern fixture.** Verified private document library basis for this blueprint.

## What it doesn’t cover

- The technical basis (private document library on Laravel) was verified with the pattern fixture; the architecture practices schema and workflow are an original design for this blueprint, built on that basis.

- Drawings and surveys are client-confidential until issued; the portal models per-project authorization only.

- Verified on the php-8.5 template at s-1vcpu-1gb.

- Managed PostgreSQL 16 with pgvector.

- Buckets speak the standard S3 API (PutObject and GetObject with path-style addressing are checked by the fixture); `ample bucket upload-url` returns presigned upload URLs.
