page:recipes:inventory manager:django:relational workspace

Host inventory manager with Django: relational workspace data

Deploy a inventory manager built with Django on Ample using the relational records 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: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true). Not separately tested: your record schema, states and access rules; treat the inventory manager-specific behavior as your application code.

Representative Queries

• Host inventory manager with Django: relational workspace data
• Where can I host Inventory manager built with Django?
• I need a workspace-specific schema, state transitions and access rules.

Resource Requirements

• primitive:compute
• primitive:postgres

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.

Execution Status

• Framework: Django
• Workload: Inventory manager
• Release Status: published
• Support Status: verified
• Execution Status: ready

Prerequisites

• A Django project that builds and starts with the documented commands (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 at runtime (auto-provisioned when omitted, or supplied with --env)
• An Ample account token with servers:write, databases:read

Tested Configuration

• Template: python-3.12
• Runtime: python
• Size: s-1vcpu-1gb
• Install: python3 -m pip install --target .ample/python -r requirements.txt
• Start: PYTHONPATH=.ample/python:${PYTHONPATH:-} python3 run.py

Input Schema

• Required: name, path, start
• Properties:
  • env: Encrypted environment variables (bucket credentials, secrets)
  • name: App name
  • path: Project directory or ample.toml service
  • release_command: Migration command run before activation
  • start: Start command (Python apps pass one explicitly)

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.
2. Implement the pattern on PostgreSQL
   • The fixture's module implements relational records: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true).
3. Deploy
   • Run the synchronous deploy once and read the result (exit 0 live, 1 failed, 2 blocked).
   • Command: ample deploy . --name --public --start "python3 run.py"
4. Verify
   • Fetch the live URL and the pattern self-test route(s) (/p/relational-records) from the example; then run your own checks.
   • Command: ample logs --kind build

Limitations

• Verified on the python-3.12 template at s-1vcpu-1gb with the example fixture; other sizes, templates and Django major versions are not verified.
• The inventory manager itself (your record schema, states and access rules) is application code and was not separately tested.
• Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Components:
  • App server (s-1vcpu-1gb, quantity: 1.0, monthlyAmount: 5.0)
  • Managed PostgreSQL database (s-1vcpu-1gb, quantity: 1.0, monthlyAmount: 5.0)