Publishing: client portal using Laravel · Ample Computer
Publishing: client portal using Laravel
A client portal blueprint for publishing built with Laravel on Ample. Domain schema: titles (isbn_or_slug, title, author, imprint, published_at): the catalog of titles; editions (title_id, format, version, object_key): editions and versioned files; customer_workspaces (name, license_type, seat_count): institutional or trade customers; customer_assets (workspace_id, title_id, object_key, license_expires_at): licensed files per customer; document_access (document_id, principal_reference, role, granted_at): who may read which document. Public information: title catalog and author pages, release schedules, rights and permissions contact. Kept out of scope until handling is reviewed: unreleased manuscripts, royalty statements, customer license keys. Manuscripts and royalty data are confidential; licensed files are authorized per customer workspace. 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
Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.Postgresverified
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
Buckets speak the S3 API with SigV4 credentials Ample Computer issues;ample bucket upload-urlreturns 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 createpassed as encrypted S3_* environment variables - A review of which publishing 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
Model the publishing domain. Create the tables titles, editions, customer_workspaces, customer_assets, document_access. The catalog of titles lives in titles; keep the sensitive classes (unreleased manuscripts, royalty statements, customer license keys) out of this schema.
Workflow step 1. Model client entities and engagement periods; every document belongs to one engagement
Workflow step 2. Authorize by client entity and role before any storage access (401 without identity, 403 for the wrong client)
Workflow step 3. Store documents in the private bucket and stream them through the app
Workflow step 4. Deploy and verify the negative authorization tests and an authorized download
Deploy. Run the synchronous deploy once and read the result. Re-running with no change is a no-op.
$ 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=...
- Verify. Run the pattern self-test(s) from the example (/p/private-document-library) and your own acceptance checks for the publishing workflow.
$ 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
- 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 Publishing 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 publishing schema and workflow are an original design for this blueprint, built on that basis.
- Manuscripts and royalty data are confidential; licensed files are authorized per customer workspace.
- 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-urlreturns presigned upload URLs.