page:recipes:admin dashboard:django:activity history

Host Admin Dashboard with Django: Application Activity History

Deploy an admin dashboard built with Django on Ample using the transactional workflows 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. Verified on Django: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected). Not separately tested: your domain records, validation rules and concurrency policy; treat the admin dashboard-specific behavior as your application code.

Representative Queries

Resource Requirements

Infrastructure Requirements

  1. Compute
    • Status: verified
    • Summary: 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
    • Status: verified
    • Summary: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

Framework

Django

Workload

Admin dashboard

Release Status

Published

Support Status

Verified

Execution Status

Ready

Prerequisites

Tested Configuration

Input Schema

{
  "type": "object",
  "properties": {
    "env": {
      "type": "array",
      "items": {
        "type": "string",
        "pattern": "^[A-Z][A-Z0-9_]*=.*$"
      },
      "maxItems": 50
    },
    "name": {
      "type": "string",
      "minLength": 1,
      "maxLength": 63,
      "pattern": "^[a-z0-9-]+$"
    },
    "path": {
      "type": "string",
      "minLength": 1,
      "maxLength": 512
    },
    "release_command": {
      "type": "string",
      "maxLength": 512
    },
    "start": {
      "type": "string",
      "maxLength": 512
    }
  },
  "required": ["name", "path", "start"],
  "additionalProperties": false
}

Workflow Steps

  1. Build and start
    • pip install into .ample/python from requirements.txt, then waitress serving project.wsgi from run.py reading PORT on the python-3.12 template. The server must bind 0.0.0.0 on PORT.
  2. Implement the pattern on PostgreSQL
    • The fixture's module implements transactional workflows: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected). Copy the approach into your schema; keep migrations idempotent and run them with --release-command.
  3. Deploy
    • Run the synchronous deploy once and read the result (exit 0 live, 1 failed, 2 blocked). Re-running with no change is a no-op.
    • Command: ample deploy . --name --public --start "python3 run.py"
  4. Verify
    • Fetch the live URL and the pattern self-test route(s) (/p/transactional-workflows) from the example; then run your own checks. On failure read ample logs --kind build then --kind runtime.
    • Command: ample logs --kind build

Examples

  1. Django pattern fixture
    • Description: Multi-pattern Django app whose transactional workflows module was checked live; the module is under tests/deploy-canaries/_pattern-modules.
    • Source Ref: tests/deploy-canaries/django-patterns

Success Checks

Limitations

Cost Estimate

Evidence Summary

  1. Canary Run
    • Summary: Django pattern fixture deployed on Ample (pip install into .ample/python from requirements.txt, then waitress serving project.wsgi from run.py reading PORT on the python-3.12 template); checks passed for transactional-workflows and configuration-secrets. Pattern proof: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected).
    • Observed At: 2026-09-20T03:31:44Z
    • Implementation Revision: 03b6402b1b3e19178985f08ea4033804521d85d4-dirty (CLI b75e104)
    • Expires At: 2027-03-19T03:31:44Z
    • Scope:
      • Checks: [/p/transactional-workflows]
      • Pattern: pattern:transactional-workflows
      • Template: python-3.12
  2. Canary Run
    • Summary: The same Django app deployed with a --release-command migration; the marker it created was readable after activation.
    • Observed At: 2026-09-20T01:54:51Z
    • Implementation Revision: 199ff1dfd52683832ae75d3f98b53a7a4bff7f96-dirty (CLI e3181f5)
    • Expires At: 2027-03-19T01:54:51Z
    • Scope:
      • Pattern: pattern:transactional-workflows

Next Actions

  1. Browse the catalog index

    • Operation ID: catalog_index
    • Method: GET
    • Relative Path: /v1/catalog

  2. Search published recipes by intent, stack, and constraints

    • Operation ID: search_recipes
    • Method: POST
    • Relative Path: /v1/catalog/search
    • Parameters:
    {"body": {"limit": 5, "query": "Host admin dashboard with Django: application activity history"}}

  3. Prepare a side-effect-free deployment plan

    • Operation ID: plan_deployment
    • Method: POST
    • Relative Path: /v1/catalog/plan
    • Parameters:
    {"body": {"inputs": {}, "projectId": "", "recipeId": "page:recipes:admin-dashboard:django:activity-history", "recipeRevision": "r1"}}

  4. Read the existing agent authentication setup

    • Operation ID: existing_auth_setup
    • Method: GET
    • Relative Path: /mcp/setup

  5. Browse Admin dashboard

    • Operation ID: browse_node
    • Method: GET
    • Relative Path: /v1/catalog/nodes/workload%3Aadmin-dashboard

  6. Browse Django

    • Operation ID: browse_node
    • Method: GET
    • Relative Path: /v1/catalog/nodes/stack%3Aframework-django

  7. Browse Transactional workflows

    • Operation ID: browse_node
    • Method: GET
    • Relative Path: /v1/catalog/nodes/pattern%3Atransactional-workflows

  8. Browse Deploy web app

    • Operation ID: browse_node
    • Method: GET
    • Relative Path: /v1/catalog/nodes/intent%3Adeploy-web-app