# Host Campaign Site with Flask: Public-Site Delivery

## Summary
Deploy a campaign site 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 campaign site-specific behavior as your application code.

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

## Resource Requirements
- **Primitive Compute**
- **Primitive CDN**

## Infrastructure Requirements
- **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.
- **CDN**
  - **Status:** Verified
  - **Summary:** The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store.

## Framework
**Flask**

## Workload
**Campaign site**

## Release Status
**Published**

## Support Status
**Verified**

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

## Tested Configuration
- **Template:** python-3.12
- **Runtime:** python
- **Size:** s-1vcpu-1gb
- **Install Command:** 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.
   ```bash
   ample deploy . --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`.
   ```bash
   ample logs  --kind build
   ```

## Examples
- **Flask pattern fixture**  
  Multi-pattern Flask app whose public web service module was checked live; the module is under tests/deploy-canaries/_pattern-modules.  
  **Source Reference:** tests/deploy-canaries/flask-patterns

## Success Checks
- **App responds on its public URL**  
  - **Kind:** http_get  
  - **Path:** /  
  - **Expect:** ample canary flask patterns
- **Versioned-static-assets self-test**  
  - **Kind:** http_get  
  - **Path:** /p/versioned-static-assets  
  - **Expect:** a CDN URL whose content is served publicly

## 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 campaign site itself (your site content and build) is application code and was not separately tested; the pattern checks are what was verified.

## Cost Estimate
- **Currency:** USD  
- **Monthly Amount:** 5.0  
- **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  
- **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.

## Next Actions
1. **Browse the catalog index**  
   - **Method:** GET  
   - **Relative Path:** /v1/catalog  
2. **Search published recipes by intent, stack and constraints**  
   - **Method:** POST  
   - **Relative Path:** /v1/catalog/search  
   - **Parameters:**  
     - **Body:** {"limit":5,"query":"Host campaign site with Flask: public-site delivery"}
3. **Prepare a side-effect-free deployment plan for an authorized project**  
   - **Method:** POST  
   - **Relative Path:** /v1/catalog/plan  
   - **Parameters:**  
     - **Body:** {"inputs":{},"projectId":"","recipeId":"page:recipes:campaign-site:flask:public-site","recipeRevision":"r1"}
4. **Read the existing agent authentication setup**  
   - **Method:** GET  
   - **Relative Path:** /mcp/setup  
5. **Browse Campaign site**  
   - **Method:** GET  
   - **Relative Path:** /v1/catalog/nodes/workload%3Acampaign-site  
6. **Browse Flask**  
   - **Method:** GET  
   - **Relative Path:** /v1/catalog/nodes/stack%3Aframework-flask  
7. **Browse Public web service**  
   - **Method:** GET  
   - **Relative Path:** /v1/catalog/nodes/pattern%3Apublic-web-service  
8. **Browse Deploy web app**  
   - **Method:** GET  
   - **Relative Path:** /v1/catalog/nodes/intent%3Adeploy-web-app