Host inventory manager with Flask: relational workspace data · Ample Computer

Host inventory manager with Flask: relational workspace data

Deploy an inventory manager built with Flask 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 Flask: 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). The inventory manager-specific behavior (your record schema, states and access rules) is your application code on that verified basis.

Verified November 5, 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 app.py
template python-3.12

Steps

  1. Build and start. pip install into .ample/python from requirements.txt, then waitress from app.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 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). 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 app.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. On failure read `ample logs <deployment_id> --kind build` then `--kind runtime`.

```bash
    $ ample logs <deployment_id> --kind build
    ```

## How it was checked

✓ app responds on its public URL · http get/ → “ample canary flask patterns”  
✓ relational-records self-test · http get/p/relational-records → “records=ok transitions=true isolation=true”

## Evidence

1. November 5, 2026 · canary run  
   Flask pattern fixture deployed on Ample (pip install into .ample/python from requirements.txt, then waitress from app.py reading PORT on the python-3.12 template); checks passed for relational-records and configuration-secrets. Pattern proof: 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).

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

## Tested examples

- **Flask pattern fixture.** Multi-pattern Flask app whose relational records module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

## What it doesn’t cover

- Verified on the python-3.12 template at s-1vcpu-1gb with the example fixture.
- The pattern checks verified the platform side; the inventory manager itself (your record schema, states and access rules) is your application code.
- Managed PostgreSQL 16 with pgvector; apps and their databases are placed together.