Host member portal with Laravel: private documents · Ample Computer
Host member portal with Laravel: private documents
Deploy a member portal built with Laravel on Ample using the private document library 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, a private S3-compatible bucket holds objects with credentials delivered as encrypted environment variables. 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). The member portal-specific behavior (your identity integration and role assignments) is your application code on that verified basis.
Verified November 6, 2026
What it runs on
Compute verified Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.
Postgres verified 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 storage verified 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 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)
A bucket from
ample bucket createwith its credentials passed as encrypted S3_* environment variablesAn Ample account token with servers:write, databases:read, buckets: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
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.
Implement the pattern on PostgreSQL. The fixture's module implements private document library: 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). Copy the approach into your schema; keep migrations idempotent and run them with --release-command.
Wire object storage. Create the bucket(s), then pass endpoint, region, bucket and keys as --env values. Use path-style addressing. Keep private data in an unpublished bucket.
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 --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=...
- Verify. Fetch the live URL and the pattern self-test route(s) (/p/private-document-library) from the example; then run your own checks. On failure read
ample logs <deployment_id> --kind buildthen--kind runtime.
$ 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 · http get/p/private-document-library → “private=ok (with ?role=owner; 401 without, 403 for viewer)”
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); checks passed for private-document-library and configuration-secrets. Pattern proof: 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).
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 private document library 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 member portal itself (your identity integration and role assignments) is your application code.
- Managed PostgreSQL 16 with pgvector; apps and their databases are placed together.
- 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.