# Host project tracker with Flask: relational workspace data

Deploy a project tracker 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). Not separately tested: your record schema, states and access rules; treat the project tracker-specific behavior as your application code.

## Summary
- **Framework**: Flask
- **Workload**: Project tracker
- **Release Status**: published
- **Support Status**: verified
- **Execution Status**: ready

## Representative Queries
- Host project tracker with Flask: relational workspace data
- Where can I host Project tracker built with Flask?
- I need a workspace-specific schema, state transitions and access rules.

## Prerequisites
1. A Flask project that builds and starts with the documented commands (pip install into .ample/python from requirements.txt, then waitress from app.py reading PORT on the python-3.12 template)
2. A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env)
3. 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 app.py

## Input Schema
```json
{
  "additionalProperties": false,
  "properties": {
    "env": {
      "description": "Encrypted environment variables (bucket credentials, secrets)",
      "items": {
        "pattern": "^[A-Z][A-Z0-9_]*=.*$",
        "type": "string"
      },
      "maxItems": 50,
      "type": "array"
    },
    "name": {
      "description": "App name",
      "maxLength": 63,
      "minLength": 1,
      "pattern": "^[a-z0-9-]+$",
      "type": "string"
    },
    "path": {
      "description": "Project directory or ample.toml service",
      "maxLength": 512,
      "minLength": 1,
      "type": "string"
    },
    "release_command": {
      "description": "Migration command run before activation",
      "maxLength": 512,
      "type": "string"
    },
    "start": {
      "description": "Start command (Python apps pass one explicitly)",
      "maxLength": 512,
      "type": "string"
    }
  },
  "required": ["name", "path", "start"],
  "type": "object"
}
```

## Workflow Steps
- **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.
- **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.
- **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 app.py"
- **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  --kind build` then `--kind runtime`. Command: ample logs  --kind build

## Success Checks
1. **App responds on its public URL**: kind: http_get, path: /, expect: ample canary flask patterns
2. **Relational-records self-test**: kind: http_get, path: /p/relational-records, expect: records=ok transitions=true isolation=true

## Limitations
- Verified on the python-3.12 template at s-1vcpu-1gb with the example fixture; other sizes, templates and Flask major versions are not verified.
- The project tracker itself (your record schema, states and access rules) is application code and was not separately tested; the pattern checks are what was verified.
- Region, compliance attestations and request-duration limits are unknown and not claimed.
- Apps auto-pause when idle and wake on the next request; always-on is an operator setting, not a plan feature.
- Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified; apps and their databases are placed together.

## Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 10.0
- **Authoritative**: true
- **Basis**: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
### Components
1. **App Server**: size s-1vcpu-1gb, quantity 1.0, monthly amount 5.0
2. **Managed PostgreSQL Database**: size s-1vcpu-1gb, quantity 1.0, monthly amount 5.0
- **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.

## Evidence Summary
1. **Kind**: canary_run,**Summary**: 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). **Observed At**: 2026-09-21T01:14:18Z
2. **Kind**: canary_run, **Summary**: The same Flask app deployed with a --release-command migration; the marker it created was readable after activation. **Observed At**: 2026-09-20T01:54:51Z

## Action Items
1. **Browse the catalog index**:  Method: GET, Path: /v1/catalog
2. **Search published recipes by intent, stack and constraints**: Method: POST, Path: /v1/catalog/search
3. **Prepare a side-effect-free deployment plan for an authorized project**: Method: POST, Path: /v1/catalog/plan
4. **Read the existing agent authentication setup**: Method: GET, Path: /mcp/setup
5. **Browse Project tracker**: Method: GET, Path: /v1/catalog/nodes/workload%3Aproject-tracker
6. **Browse Flask**: Method: GET, Path: /v1/catalog/nodes/stack%3Aframework-flask
7. **Browse Relational records**: Method: GET, Path: /v1/catalog/nodes/pattern%3Arelational-records
8. **Browse Deploy web app**: Method: GET, Path: /v1/catalog/nodes/intent%3Adeploy-web-app