Host knowledge base with Flask: public-site delivery

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

Representative Queries

• Host knowledge base with Flask: public-site delivery
• Where can I host Knowledge base built with Flask?
• I need an explicit origin-to-CDN delivery path and a tested public content build.

Resource Requirements

• Compute
• CDN

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

Knowledge base

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: 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. 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 --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

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.

Success Checks

1. App responds on its public URL
   • Kind: http_get
   • Path: /
   • Expect: ample canary flask patterns
2. 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 knowledge base itself (your site content and build) 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.
• PutObject and GetObject with path-style addressing are verified; multipart upload, listing, presigned URLs and lifecycle rules are not.
• The CDN serves published-bucket objects only; cache rules, purge and TTL control are not verified (the fixture sets Cache-Control on upload and versions keys).

Cost Estimate

• Currency: USD
• Monthly Amount: 5.0
• Authoritative: true
• Basis: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
• Components:
  • Name: 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.

Evidence Summary

1. Kind: canary_run
   • Summary: Flask pattern fixture deployed on Ample; checks passed for versioned-static-assets and configuration-secrets. Pattern proof.
2. Kind: canary_run
   • Summary: The same Flask app deployed with a --release-command migration; the marker it created was readable after activation.

Next 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 existing agent authentication setup
• Browse Knowledge base
• Browse Flask
• Browse Public web service
• Browse Deploy web app