# Host company website with Flask: public-site delivery

Deploy a company website built with Flask on Ample using the public web service pattern. Compute runs the app in an isolated microVM behind a public HTTPS URL, and a published bucket serves public assets from the CDN host. Verified on Flask: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL alongside the app's own public HTTPS URL. Not separately tested: your site content and build; treat the company website-specific behavior as your application code.

## Summary
- **Framework**: Flask  
- **Workload**: Company website  
- **Release Status**: published  
- **Support Status**: verified  
- **Execution Status**: ready

## Representative Queries
- Host company website with Flask: public-site delivery  
- Where can I host Company website built with Flask?  
- I need an explicit origin-to-CDN delivery path and a tested public content build.

## 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 bucket from `ample bucket create` with its credentials passed as encrypted S3_* environment variables  
3. An Ample account token with servers:write, buckets:read

## Input Schema
```json
{
  "env": [
    "ENV_VAR=value"
  ],
  "name": "app-name",
  "path": "/path/to/project",
  "release_command": "command to run",
  "start": "start command"
}
```

## Tested Configuration
- **Template**: python-3.12  
- **Runtime**: python  
- **Size**: s-1vcpu-1gb  
- **Install**: python3 -m pip install --target .ample/python -r requirements.txt  
- **Start Command**: 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. **Wire object storage**: Create the bucket(s), then pass endpoint, region, bucket and keys as --env values. Use path-style addressing. Keep private data in an unpublished bucket. Publish only the bucket that serves public assets and reference its CDN URL.
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 <name> --public --start "python3 app.py" --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=... --env CDN_PUBLIC_URL=...`
4. **Verify**: Fetch the live URL and the pattern self-test route(s) (/p/versioned-static-assets) 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
- **App responds** on its public URL  
- **Versioned-static-assets** self-test

## 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 company website itself (your site content and build) is application code and was not separately tested.

## Cost Estimate
- **Currency**: USD  
- **Monthly Amount**: 5.0  
- **Basis**: size prices from pricing.toml (loaded by the API)  
- **Components**:
   - App server: s-1vcpu-1gb (1.0)
- **Note**: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

## Examples
- **Flask pattern fixture**: Multi-pattern Flask app whose public web service module was checked live; location: `tests/deploy-canaries/flask-patterns`.