Host help desk with Laravel: downloadable reports · Ample Computer

Host help desk with Laravel: downloadable reports

Deploy a help desk built with Laravel on Ample using the generated downloads 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: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3). The help desk-specific behavior (your export formats, retention policy and entitlement model) is your application code on that verified basis.

supportverifiedreleasepublishedagent runready

VerifiedNovember 6, 2026

What it runs on

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 create with its credentials passed as encrypted S3_* environment variables

An Ample account token with servers:write, databases:read, buckets:read

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. 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 generated downloads: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3). Copy the approach into your schema; keep migrations idempotent and run them with --release-command.

  3. 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.

  4. 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=...
  1. Verify. Fetch the live URL and the pattern self-test route(s) (/p/generated-downloads) 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”

✓generated-downloads self-test· http get/p/generated-downloads → “export=ok rows=3 (with ?token=...; 401 without)”

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 generated-downloads and configuration-secrets. Pattern proof: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3).

  1. 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 generated downloads 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 help desk itself (your export formats, retention policy and entitlement model) 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-url returns presigned upload URLs.