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. Kept out of scope until handling is reviewed: customer API keys and usage logs, private integration details. API keys and usage logs are secrets or personal data; keep them out of documentation workflows.

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

Framework

• Framework: Laravel
• Workload: Asset library
• Industry: Developer tools

Release Status

• Release Status: published
• Support Status: verified
• Execution Status: ready

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
• A review of which developer tools data classes may be handled at all; this blueprint models public information only.

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

Workflow Steps

1. Model the developer tools domain
   • Create the tables customer_workspaces, doc_versions, sdk_releases, customer_assets, uploads. Customer organizations lives in customer_workspaces; keep the sensitive classes (customer API keys and usage logs, private integration details) out of this schema.
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. Re-running with no change is a no-op.
   • Command: ample deploy . --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.
   • Command: ample logs --kind build.

Costs

• Currency: USD
• Monthly Amount: 10.0
• Basis: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
• Components:
  • app server: s-1vcpu-1gb, 1.0, 5.0
  • managed PostgreSQL database: s-1vcpu-1gb, 1.0, 5.0
  • Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.

Next Actions

• Browse the catalog: /v1/catalog
• Search published recipes: /v1/catalog/search with query "Developer tools: asset library using Laravel"
• Prepare a deployment plan: /v1/catalog/plan
• Read existing authentication setup: /mcp/setup
• Browse Developer tools: /v1/catalog/nodes/industry%3Adeveloper-tools
• Browse Asset library: /v1/catalog/nodes/workload%3Aasset-library
• Browse Laravel: /v1/catalog/nodes/stack%3Aframework-laravel
• Browse Deploy web app: /v1/catalog/nodes/intent%3Adeploy-web-app