Travel operators: public directory using Django

Summary

A public directory blueprint for travel operators built with Django on Ample. Domain schema:

• Listings: trips as listings with publishing status
• Agencies: operators or branches
• Suppliers: hotels and transport suppliers
• Reports: branch sales reports
• State transitions: the allowed state machine.

Public information includes published trips and departure dates, destination guides, and booking conditions. Certain sensitive information has been explicitly kept out of scope until handling is reviewed.

Representative Queries

• Travel operators: public directory using Django
• Where can I host Travel operators: Public directory built with Django?
• I need a genuinely specialized public directory workflow covering tour listings, supplier access, and itinerary reporting.

Resource Requirements

• Primitive Compute
• Primitive Postgres
• Primitive CDN

Infrastructure Requirements

1. Compute: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle;
2. Postgres: Managed PostgreSQL 16 runs in a microVM and is auto-provisioned when an app needs a database;
3. CDN: The CDN host serves objects from published buckets.

Framework

• Django

Workload

• Public directory

Industry

• Travel operators

Release Status

Published

Support Status

Verified

Execution Status

Ready

Prerequisites

• A Django project (pip install into .ample/python from requirements.txt)
• A PostgreSQL driver reading DATABASE_URL
• Bucket credentials 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.

Tested Configuration

• Template: python-3.12
• Runtime: python
• Size: s-1vcpu-1gb

Workflow Steps

1. Model the travel operators domain: Create the tables listings, agencies, suppliers, reports, state_transitions.
2. Workflow step 1: Model listings with a publishing_status state machine scoped to the agency.
3. Workflow step 2: Serve only published listings, with media from the CDN bucket.
4. Workflow step 3: Enforce the agency scope on every query.
5. Workflow step 4: Deploy and verify a published listing and that unpublished listings are absent.
6. Deploy: Run the synchronous deploy once and read the result.
7. Verify: Run the pattern self-test and your own acceptance checks for the travel operators workflow.

Examples

1. Django pattern fixture: Verified relational records basis for this blueprint.

Success Checks

1. App responds on its public URL: ample canary django patterns
2. Relational-records self-test from the example: see the pattern fixture checks.

Limitations

1. No health, financial, privacy, or other compliance claim is made.
2. Verified on the python-3.12 template at s-1vcpu-1gb.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Components:
  • App server: 5.0
  • Managed PostgreSQL database: 5.0

Evidence Summary

• The blueprint's Travel operators schema and workflow build on a verified basis and were not separately executed.

Last Verified At

2026-09-20T03:31:44Z

Next Actions

1. Browse the catalog index: /v1/catalog
2. Search published recipes by intent: /v1/catalog/search
3. Prepare a side-effect-free deployment plan: /v1/catalog/plan