Developer tools: asset library using Laravel

Summary

A asset library blueprint for developer tools built with Laravel on Ample. Domain schema: customer_workspaces (name, plan, api_key_count): customer organizations; doc_versions (product_version, title, object_key, published_at): versioned reference docs and guides; sdk_releases (language, version, changelog_object_key, released_at): SDK releases and changelogs; customer_assets (workspace_id, title, object_key, visibility): customer-specific artifacts; uploads (id, owner_reference, object_key, content_type, size, uploaded_at): validated uploads linked to their owner. Public information: versioned API reference and guides, SDK release notes, status page links. Technical basis verified on Laravel: content-type and size validation that rejects disallowed files, an object written to a private bucket and a row linking the record to the object key (reject=ok upload=ok linked=ok).

Infrastructure requirements

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

Prerequisites

• 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

Exact tested configuration

• template: php-8.5
• runtime: php
• size: s-1vcpu-1gb
• install: composer install --no-dev --prefer-dist --no-interaction --no-progress --optimize-autoloader
• start: frankenphp php-server --listen :$PORT --root public

Steps

1. Model the developer tools domain. Create the tables customer_workspaces, doc_versions, sdk_releases, customer_assets, uploads.
2. Workflow step 1. Model assets linked to their owning group or workspace
3. Workflow step 2. Validate uploads and store them in the private bucket; link each object to its row
4. Workflow step 3. Authorize downloads by membership
5. Workflow step 4. Deploy and verify rejection of disallowed files and a linked upload
6. Deploy. Run the synchronous deploy once and read the result.

   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/browser-file-uploads) and your own acceptance checks for the developer tools workflow.

   ample logs <deployment_id> --kind build

Tested examples

• Laravel pattern fixture (tests/deploy-canaries/laravel-patterns): Verified browser file uploads basis for this blueprint.

Success checks

• app responds on its public URL (/ on the live URL, expect ample canary laravel patterns)
• browser-file-uploads self-test from the example (/p/browser-file-uploads on the live URL, expect see the pattern fixture checks)

Limitations

• The technical basis (browser file uploads on Laravel) was verified with the pattern fixture; the developer tools schema and workflow are an original design for this blueprint and were not executed as a separate application.
• No health, financial, privacy or other compliance claim is made.

Cost estimate

Estimated 10.00 USD per month.

• app server x1 s-1vcpu-1gb: 5.00 USD
• managed PostgreSQL database x1 s-1vcpu-1gb: 5.00 USD

Verification evidence

• canary_run on 2026-09-20T20:36:21Z at revision 118ad1c6d7d23d4c2ce069254bab9ec9d37cd57b-dirty (CLI 118ad1c)

Execution binding

MCP tool ample_deploy, schema hash 876465fce906da0c observed 2026-09-21T03:19:59.461917+00:00 at revision 49962bcade4f, binding state current, required scopes: servers:write, databases:read, buckets:read.