page:blueprints:developer tools:asset library:next js

Developer tools: asset library using Next.js

Summary

A asset library blueprint for developer tools built with Next.js 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 Next.js: 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).

Representative Queries

• Developer tools: asset library using Next.js
• Where can I host Developer tools: Asset library built with Next.js?
• I need a genuinely specialized asset library workflow covering organization access, versioned technical docs and build artifacts.

Infrastructure Requirements

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

Workflow Steps

1. Model the developer tools domain: Create the tables customer_workspaces, doc_versions, sdk_releases, customer_assets, uploads. Customer organizations live in customer_workspaces; keep the sensitive classes (customer API keys and usage logs, private integration details) out of this schema.
2. Model assets linked to their owning group or workspace.
3. Validate uploads and store them in the private bucket; link each object to its row.
4. Authorize downloads by membership.
5. 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=...
6. 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

• Monthly Amount: $10.00
  • App server: 1 x s-1vcpu-1gb = $5.00
  • Managed PostgreSQL database: 1 x s-1vcpu-1gb = $5.00
  • 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.

Success Checks

• App responds on its public URL: ample canary next js patterns
• Browser-file-uploads self-test from the example: see the pattern fixture checks

Limitations

• The technical basis (browser file uploads on Next.js) 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.
• API keys and usage logs are secrets or personal data; keep them out of documentation workflows.
• Verified on the node-22 template at s-1vcpu-1gb; region, request-duration limits and other sizes are unknown or unverified.
• Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified.