# Host Reporting Dashboard with Flask: File Attachments

Deploy a reporting dashboard built with Flask on Ample using the browser file uploads 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. Verified on Flask: content-type and size validation that rejects disallowed files, an object written to a private bucket and a row linking the record to the object key (reject=ok upload=ok linked=ok). The reporting dashboard-specific behavior (your upload UI, allowed types, size limits and virus scanning) is your application code on that verified basis.

## What It Runs On

- [Compute](/content/discover/primitive/compute/index.html)  
  Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.

- [Postgres](/content/discover/primitive/postgres/index.html)  
  Managed PostgreSQL 16 with pgvector runs in its own microVM and is auto-provisioned when an app needs a database and no `DATABASE_URL` is supplied.

- [S3-compatible Object Storage](/content/discover/primitive/s3-compatible-object-storage/index.html)  
  Buckets speak the S3 API with SigV4 credentials Ample Computer issues; `ample bucket upload-url` returns a presigned upload URL. PutObject and GetObject are checked by canary.

## You Need

- 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

- An Ample account token with `servers:write`, `databases:read`, `buckets:read`

## Exact Tested Configuration

```bash
install
python3 -m pip install --target .ample/python -r requirements.txt

runtime
python

sizes-1vcpu-1gb

start
PYTHONPATH=.ample/python:${PYTHONPATH:-} python3 app.py

template
python-3.12
```

## 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 browser file uploads: content-type and size validation that rejects disallowed files, an object written to a private bucket and a row linking the record to the object key (reject=ok upload=ok linked=ok). 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.

4. **Deploy.** Run the synchronous deploy once and read the result (exit 0 live, 1 failed, 2 needs an answer first). Re-running with no change is a no-op.

```bash
    $ ample deploy . --name <app-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=...
    ```

5. **Verify.** Fetch the live URL and the pattern self-test route(s) (/p/browser-file-uploads) from the example; then run your own checks. On failure read `ample logs <deployment_id> --kind build` then `--kind runtime`.

```bash
    $ ample logs <deployment_id> --kind build
    ```

## How It Was Checked

✓ app responds on its public URL · `http get/` → “ample canary flask patterns”  
✓ browser-file-uploads self-test · `http get/p/browser-file-uploads` → “reject=ok upload=ok linked=ok”

## Evidence

1. November 5, 2026 · canary run  
   Flask pattern fixture deployed on Ample (pip install into `.ample/python` from `requirements.txt`, then `waitress` from `app.py` reading `PORT` on the python-3.12 template); checks passed for browser-file-uploads and configuration-secrets. Pattern proof: content-type and size validation that rejects disallowed files, an object written to a private bucket and a row linking the record to the object key (reject=ok upload=ok linked=ok).

2. November 6, 2026 · canary run  
   The same Flask app deployed with a --release-command migration; the marker it created was readable after activation.

## Tested Examples

- **Flask pattern fixture.** Multi-pattern Flask app whose browser file uploads module was checked live; the module is under `tests/deploy-canaries/_pattern-modules`.

## What It Doesn’t Cover

- Verified on the python-3.12 template at `s-1vcpu-1gb` with the example fixture.
- The pattern checks verified the platform side; the reporting dashboard itself (your upload UI, allowed types, size limits and virus scanning) is your application code.
- Managed PostgreSQL 16 with pgvector; apps and their databases are placed together.
- Buckets speak the standard S3 API (PutObject and GetObject with path-style addressing are checked by the fixture); `ample bucket upload-url` returns presigned upload URLs.
