page:recipes:partner portal:flask:public profiles

Host partner portal with Flask: public profile assets

Deploy a partner portal built with Flask on Ample using the public image delivery 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, a private S3-compatible bucket holds objects with credentials delivered as encrypted environment variables, and a published bucket serves public assets from the CDN host. Verified on Flask: public objects in a published bucket served from the CDN URL, kept separate from private objects in an unpublished bucket that require authorization (private=ok only for the allowed role). Not separately tested: your image processing and profile-media rules; treat the partner portal-specific behavior as your application code.

Representative Queries

• Host partner portal with Flask: public profile assets
• Where can I host Partner portal built with Flask?
• I need separate public profile media from private data, with CDN cache rules.

Resource Requirements

• Compute
• PostgreSQL
• S3-compatible object storage
• CDN

Infrastructure Requirements

1. Compute: 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: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.
3. S3-compatible object storage: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.
4. CDN: The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store.

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)
• A bucket from ample bucket create with its credentials passed as encrypted S3_* environment variables and a second, published bucket for public assets (CDN_*)
• An Ample account token with servers:write, databases:read, buckets: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 public image delivery: public objects in a published bucket served from the CDN URL, kept separate from private objects in an unpublished bucket that require authorization (private=ok only for the allowed role). Copy the approach into your schema; keep migrations idempotent and run them with --release-command.
3. 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.
4. 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=...
5. Verify: Fetch the live URL and the pattern self-test route(s) (/p/public-media-library, /p/private-document-library) 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 image delivery 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
• Public-media-library self-test
• Private-document-library 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 partner portal itself (your image processing and profile-media rules) is application code and was not separately tested.
• Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Basis: size prices from pricing.toml (loaded by the API)
• Components:
  1. App server: s-1vcpu-1gb (quantity: 1.0, monthlyAmount: 5.0)
  2. Managed PostgreSQL database: s-1vcpu-1gb (quantity: 1.0, monthlyAmount: 5.0)

Evidence Summary

1. Canary run: Flask pattern fixture deployed on Ample; checks passed for public-media-library, private-document-library and configuration-secrets.

   • Observed At: 2026-09-21
   • Implementation Revision: 50dbac567d2c5cc8e55e6c748a646be0025d9cfb-dirty
   • Expires At: 2027-03-20

2. Canary run: The same Flask app deployed with a --release-command migration; the marker it created was readable after activation.

   • Observed At: 2026-09-20
   • Implementation Revision: 199ff1dfd52683832ae75d3f98b53a7a4bff7f96-dirty
   • Expires At: 2027-03-19

Next Actions

• Browse the catalog index GET /v1/catalog
• Search published recipes by intent POST /v1/catalog/search
• Prepare a side-effect-free deployment plan POST /v1/catalog/plan