# Host Partner Portal with Flask: Application Activity History

Deploy a partner portal built with Flask 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 Flask: 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 partner portal-specific behavior as your application code.

## Representative Queries
- Host partner portal with Flask: application activity history
- Where can I host Partner portal built with Flask?
- I need an application-owned event schema and tested history queries; not native platform audit logs.

## Resource Requirements
- **Compute**  
- **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.

## Framework
Flask  
## Workload
Partner portal

## Execution Status
Ready

## Prerequisites
- 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)  
- 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

## Workflow 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 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 app.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
- **Flask Pattern Fixture**  
   - Multi-pattern Flask app whose transactional workflows module was checked live; the module is under tests/deploy-canaries/_pattern-modules.  
   - Source Ref: tests/deploy-canaries/flask-patterns

## Success Checks
1. **App Responds on its Public URL**  
   - Kind: http_get  
   - Path: /  
   - Expect: ample canary flask patterns  
2. **Transactional Workflows Self-Test**  
   - Kind: http_get  
   - Path: /p/transactional-workflows  
   - Expect: tx=ok history=2 conflict=rejected

## 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 partner portal itself (your domain records, validation rules and concurrency policy) 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  
- **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.  
   - 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

## Last Verified At
2026-09-21T01:14:18Z

## Forward Actions
- Browse the catalog index  
- Search published recipes by intent, stack and constraints  
- Prepare a side-effect-free deployment plan for an authorized project  
- Read the existing agent authentication setup  
- Browse Partner portal  
- Browse Flask  
- Browse Transactional workflows  
- Browse Deploy web app