page:blueprints:architecture practices:client portal:laravel

Architecture practices: client portal using Laravel

A client portal blueprint for architecture practices built with Laravel on Ample. Domain schema:

Public information includes: portfolio and services, team and accreditations, studio locations. Drawings and surveys are client-confidential until issued; the portal models per-project authorization only.

Representative Queries

Resource Requirements

Infrastructure Requirements

  1. Compute: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
  2. 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.
  3. S3-compatible object storage: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary.

Framework and Workload

Prerequisites

Tested Configuration

Workflow Steps

  1. Model the architecture practices domain: Create the tables client_entities, projects, drawing_sets, approvals, document_access.
  2. Model client entities and engagement periods; every document belongs to one engagement.
  3. Authorize by client entity and role before any storage access.
  4. Store documents in the private bucket and stream them through the app.
  5. Deploy and verify the negative authorization tests and an authorized download.
  6. Run the synchronous deploy once and read the result. Re-running with no change is a no-op.
  7. Run the pattern self-test(s) from the example and your own acceptance checks for the architecture practices workflow.

Cost Estimate

Limitations

Evidence Summary

Next Actions