## Travel operators: reporting dashboard using Django

### Summary
A reporting dashboard blueprint for travel operators built with Django on Ample. 
Domain schema: 
- **Listings** (reference, destination, departure_dates, price_from, publishing_status, agency_id): trips as listings with publishing status. 
- **Agencies** (name, license_number, region): operators or branches. 
- **Suppliers** (name, type, agency_id, status): hotels and transport suppliers. 
- **Reports** (agency_id, period, object_key, generated_at): branch sales reports. 
- **Exports** (id, definition, object_key, row_count, generated_at, authorized_role): generated artifacts and who may download them.

Public information: published trips and departure dates, destination guides, booking conditions. 
Kept out of scope until handling is reviewed: traveler passports and identity, payment details, supplier contracts. 
Passport and payment data are regulated; only published trips and branch reporting are modeled. 
Technical basis verified on Django: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3).

### Representative Queries
- Travel operators: reporting dashboard using Django
- Where can I host Travel operators: Reporting dashboard built with Django?
- I need a genuinely specialized reporting dashboard workflow covering tour listings, supplier access and itinerary reporting.

### Resource Requirements
- primitive:compute
- primitive:postgres
- primitive:s3-compatible-object-storage

### 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. **Postgres**  
   - Status: verified  
   - Summary: 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**  
   - Status: verified  
   - Summary: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

### Framework
- **Framework**: Django  
- **Workload**: Reporting dashboard  
- **Industry**: Travel operators  
- **Release Status**: published  
- **Support Status**: verified  
- **Execution Status**: ready  
- **Docs Only**: false

### Prerequisites
- A Django project (pip install into .ample/python from requirements.txt, then waitress serving project.wsgi from run.py reading PORT on the python-3.12 template)  
- A PostgreSQL driver reading DATABASE_URL (auto-provisioned when omitted)  
- Bucket credentials from `ample bucket create` passed as encrypted S3_* environment variables  
- A review of which travel operators data classes may be handled at all; this blueprint models public information only.

### Workflow Steps
1. **Model the travel operators domain**  
   Create the tables listings, agencies, suppliers, reports, exports. Trips as listings with publishing status lives in listings; keep the sensitive classes (traveler passports and identity, payment details, supplier contracts) out of this schema.

2. **Workflow step 1**  
   Model report definitions scoped to the agency

3. **Workflow step 2**  
   Generate report artifacts from queries and store them with metadata

4. **Workflow step 3**  
   Authorize downloads (401 without identity)

5. **Workflow step 4**  
   Deploy and verify an authorized export and the rejected anonymous request

6. **Deploy**  
   Run the synchronous deploy once and read the result. Re-running with no change is a no-op.
   Command: `ample deploy . --name  --public --start "python3 run.py" --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=...`

7. **Verify**  
   Run the pattern self-test(s) from the example (/p/generated-downloads) and your own acceptance checks for the travel operators workflow.
   Command: `ample logs  --kind build`

### Examples
- **Django pattern fixture**  
  Verified generated downloads basis for this blueprint.
  Source Ref: tests/deploy-canaries/django-patterns

### Success Checks
1. App responds on its public URL: 
   - Kind: `http_get`   
   - Path: `/`  
   - Expect: `ample canary django patterns`

2. generated-downloads self-test from the example: 
   - Kind: `http_get`  
   - Path: `/p/generated-downloads`  
   - Expect: `see the pattern fixture checks`

### Limitations
- The technical basis (generated downloads on Django) was verified with the pattern fixture; the travel operators schema and workflow are an original design for this blueprint and were not executed as a separate application.
- No health, financial, privacy or other compliance claim is made. Passport and payment data are regulated; only published trips and branch reporting are modeled.
- Public content and synthetic examples only until actual data-handling requirements have been reviewed. 
- Verified on the python-3.12 template at s-1vcpu-1gb; region, request-duration limits and other sizes are unknown or unverified.  
- Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified.  
- PutObject and GetObject with path-style addressing are verified; other S3 operations and CDN cache rules are not.

### Cost Estimate
- **Currency**: USD  
- **Monthly Amount**: 10.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  
  - Managed PostgreSQL database: 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
- **Kind**: canary_run  
  Summary: Django pattern fixture deployed on Ample (pip install into .ample/python from requirements.txt, then waitress serving project.wsgi from run.py reading PORT on the python-3.12 template); the generated downloads checks passed: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3). The blueprint's Travel operators schema and workflow below build on that verified basis and were not separately executed.  
  - Observed At: 2026-09-20T03:31:44Z  
  - Implementation Revision: `03b6402b1b3e19178985f08ea4033804521d85d4-dirty (CLI b75e104)`  
  - Expires At: 2027-03-19T03:31:44Z  
  - Scope: checks: ["/p/generated-downloads"], pattern: "pattern:generated-downloads", template: "python-3.12"

### Last Verified At
- 2026-09-20T03:31:44Z

### Formats
- **HTML**: [Link](/content/blueprints/travel-operators/reporting-dashboard/django/index.html)  
- **Markdown**: [Link](/content/blueprints/travel-operators/reporting-dashboard/django.md)  
- **JSON**: [Link](https://api.ample.computer/v1/catalog/recipes/page%3Ablueprints%3Atravel-operators%3Areporting-dashboard%3Adjango)

### Next Actions
1. **Browse the catalog index**  
   - Action ID: browse-catalog  
   - Method: GET  
   - Relative Path: `/v1/catalog`

2. **Search published recipes by intent, stack and constraints**   
   - Action ID: search-recipes  
   - Method: POST  
   - Relative Path: `/v1/catalog/search`  
   - Parameters: {"body":{"limit":5,"query":"Travel operators: reporting dashboard using Django"}}

3. **Prepare a side-effect-free deployment plan for an authorized project**   
   - Action ID: plan:page:blueprints:travel-operators:reporting-dashboard:django  
   - Method: POST  
   - Relative Path: `/v1/catalog/plan`

4. **Read the existing agent authentication setup**   
   - Action ID: auth-setup  
   - Method: GET  
   - Relative Path: `/mcp/setup`

5. **Browse Travel operators**  
   - Action ID: browse:industry:travel-operators  
   - Method: GET  
   - Relative Path: `/v1/catalog/nodes/industry%3Atravel-operators`

6. **Browse Reporting dashboard**  
   - Action ID: browse:workload:reporting-dashboard  
   - Method: GET  
   - Relative Path: `/v1/catalog/nodes/workload%3Areporting-dashboard`

7. **Browse Django**  
   - Action ID: browse:stack:framework-django  
   - Method: GET  
   - Relative Path: `/v1/catalog/nodes/stack%3Aframework-django`

8. **Browse Deploy web app**   
   - Action ID: browse:intent:deploy-web-app  
   - Method: GET  
   - Relative Path: `/v1/catalog/nodes/intent%3Adeploy-web-app`