page:blueprints:developer tools:asset library:django

Developer tools: Asset library using Django

Summary

A asset library blueprint for developer tools built with Django 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.

Requirements

Resource Requirements

• primitive:compute
• primitive:postgres
• primitive:s3-compatible-object-storage

Infrastructure Requirements

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

Prerequisites

• A Django project (pip install into .ample/python from requirements.txt, then waitress serving project.wsgi from run.py reading PORT on the python-3.12 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.

Workflow Steps

1. Model the developer tools domain: Create the tables customer_workspaces, doc_versions, sdk_releases, customer_assets, uploads.
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 and verify rejection of disallowed files and a linked upload.
6. Run the synchronous deploy once and read the result. Re-running with no change is a no-op.

Examples

• Title: Django pattern fixture
  Description: Verified browser file uploads basis for this blueprint.
  Source Reference: tests/deploy-canaries/django-patterns

Limitations

• The technical basis (browser file uploads on Django) 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. API keys and usage logs are secrets or personal data; keep them out of documentation workflows.
• Public content and synthetic examples only until actual data-handling requirements have been reviewed.

Cost Estimate

• Currency: USD
• Monthly Amount: $10.00
• Basis: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
• Components:
  • App server (Size: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: $5.00)
  • Managed PostgreSQL database (Size: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: $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.

Next Actions

1. Browse the catalog index - GET /v1/catalog
2. Search published recipes by intent, stack and constraints - POST /v1/catalog/search
3. Prepare a side-effect-free deployment plan for an authorized project - POST /v1/catalog/plan
4. Read the existing agent authentication setup - GET /mcp/setup
5. Browse Developer tools - GET /v1/catalog/nodes/industry%3Adeveloper-tools
6. Browse Asset library - GET /v1/catalog/nodes/workload%3Aasset-library
7. Browse Django - GET /v1/catalog/nodes/stack%3Aframework-django
8. Browse Deploy web app - GET /v1/catalog/nodes/intent%3Adeploy-web-app