Host storefront with Django: relational catalog data · Ample Computer

Host storefront with Django: relational catalog data

Deploy a storefront 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). The storefront-specific behavior (your domain records, validation rules and concurrency policy) is your application code on that verified basis.

supportverifiedreleasepublishedagent runready

Verified November 6, 2026

What it runs on

You need

Exact tested configuration

install

python3 -m pip install --target .ample/python -r requirements.txt  

runtime

python  

sizes

1vcpu-1gb  

start

PYTHONPATH=.ample/python:${PYTHONPATH:-} python3 run.py  

template

python-3.12  

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 needs an answer first). Re-running with no change is a no-op.

    $ ample deploy . --name <app-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 <deployment_id> --kind build then --kind runtime.

    $ ample logs <deployment_id> --kind build  
    

How it was checked

✓ app responds on its public URL· http get/ → “ample canary django patterns”

✓ transactional-workflows self-test· http get/p/transactional-workflows → “tx=ok history=2 conflict=rejected”

Evidence

  1. November 6, 2026 · canary run
    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).

  2. November 6, 2026 · canary run
    The same Django app deployed with a --release-command migration; the marker it created was readable after activation.

Tested examples

What it doesn’t cover