## Host member portal with Flask: application activity history

Deploy a member 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 member portal-specific behavior as your application code.

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

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

### Framework
- Flask

### Workload
- Member portal

### Release Status
- Published

### Support Status
- Verified

### Execution Status
- Ready

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

### 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.  
  `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`.  
  `ample logs --kind build`

### Success Checks
- **App responds on its public URL**  
  **Kind:** http_get  
  **Path:** /  
  **Expect:** ample canary flask patterns

- **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 member 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
- **Authoritative:** true
- **Basis:** size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
- **Components:**
  - **App server:**  
  - **Size:** s-1vcpu-1gb  
  - **Quantity:** 1.0  
  - **Monthly Amount:** 5.0
  - **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.