TripRep

TripRep is a Django web app for travelers who want one place to store and review trip tickets and do much more.
You can upload ticket PDFs, store trip details, view a clean list of past tickets, and track simple spending statistics. In addition, TripRep comes with AI agents that can help you book flight tickets, create itineraries, and help answer travel questions.

The app also includes an AI-assisted flow that reads a ticket PDF and auto-fills ticket fields using Google Gemini.

Table of Contents

• What TripRep Does
• Tech Stack
• Project Structure
• Getting Started
• Environment Variables
• Run the App
• How to Use TripRep
• Route Guide
• Troubleshooting
• Production and Security Notes
• Contributing

What TripRep Does

TripRep currently focuses on ticket management:

• User signup, login, logout, and profile updates
• Ticket creation with manual entry fields
• Ticket PDF upload and thumbnail generation (first page preview)
• AI extraction endpoint to read uploaded PDF tickets and prefill fields
• Ticket list view and individual ticket detail pages
• Basic statistics page (ticket count and spending)
• AI agents to book tickets and create itineraries (in progress)

Tech Stack

• Python 3
• Django 4.2+
• SQLite (default local database)
• google-genai for Gemini ticket parsing
• PyMuPDF (fitz) + Pillow for ticket thumbnail generation

Project Structure

TripRep/
├── manage.py
├── requirements.txt
├── README.md
├── TripRep/
│   ├── settings.py
│   ├── urls.py
│   └── wsgi.py
└── core/
    ├── models.py
    ├── views.py
    ├── urls.py
    ├── forms.py
    ├── signals.py
    ├── templates/core/
    └── static/

Getting Started

1. Clone the repository

git clone <your-repo-url>
cd TripRep

2. Create and activate a virtual environment

Linux/macOS:

python3 -m venv .venv
source .venv/bin/activate

Windows PowerShell:

python -m venv .venv
.\.venv\Scripts\Activate.ps1

3. Install dependencies

pip install -r requirements.txt

4. Configure environment variables

Create a .env file in the project root:

genai_api_key=YOUR_GOOGLE_GENAI_API_KEY

Important: the key name is genai_api_key (lowercase), matching TripRep/settings.py.

5. Run migrations

python manage.py migrate

During migration, a default superuser is auto-created by core/signals.py:

• Username: hrajora
• Password: hrajora

This is for local development only. Change or remove this behavior before any production use.

Environment Variables

TripRep currently reads:

• genai_api_key: API key used by the Gemini integration in ticket extraction.

If this is missing, AI ticket processing (/create_ticket/) will fail.

Run the App

Start the development server:

python manage.py runserver

Open:

• App home: http://127.0.0.1:8000/
• Login: http://127.0.0.1:8000/login/
• Admin: http://127.0.0.1:8000/admin/

How to Use TripRep

Flow 1: Create an account and access dashboard

1. Visit /signup/
2. Register with name, email, and password
3. After signup/login, go to /dashboard/

Flow 2: Add a ticket manually

1. Go to /add_ticket/
2. Upload a ticket PDF
3. Fill in title, source, destination, type, booked-through, date, and amount
4. Submit to save ticket

Flow 3: Use AI ticket extraction

1. On /add_ticket/, select a PDF
2. Frontend JS posts the file to /create_ticket/
3. Backend calls Gemini, parses the response, and returns extracted fields
4. Form fields auto-populate in the browser
5. Submit to persist the ticket

Flow 4: Review saved tickets

1. Open /tickets/ for your personal ticket list
2. Click a ticket to open /view_ticket/<ticket_id>/
3. View metadata, thumbnail, and downloadable file
4. Delete a ticket from the ticket detail page if needed

Flow 5: View summary stats

Open /statistics/ to see:

• Total ticket count
• Total spending amount
• Counts grouped by ticket type

Route Guide

Main user-facing routes from core/urls.py:

• / home page
• /about_triprep/ about page
• /signup/ user registration
• /login/ user login
• /logout/ user logout
• /dashboard/ post-login dashboard
• /profile/ profile page
• /update_profile/ profile update action
• /tickets/ ticket listing
• /add_ticket/ add ticket form
• /create_ticket/ AI extraction endpoint (POST)
• /save_ticket/ save ticket endpoint (POST)
• /view_ticket/<ticket_id>/ ticket details
• /delete_ticket/<ticket_id>/ delete ticket
• /statistics/ ticket statistics
• /reservations/ reservations page (currently minimal)

Troubleshooting

AI extraction fails

• Verify .env exists in project root.
• Confirm genai_api_key is valid.
• Ensure uploaded file is a readable PDF.

Ticket thumbnail not generated

• Check that PyMuPDF and Pillow installed correctly.
• Confirm uploaded file is not corrupted.
• Ensure media files are writable in your environment.

Static or media files not showing in development

• Keep DEBUG = True for local development.
• Confirm URLs are loaded through Django (/static/..., /media/...).

Login issues

• Ensure migrations completed successfully.
• Use the default local superuser only for local testing or create a new user in admin.

Production and Security Notes

Before deployment, update the following:

• Remove or secure auto-created default superuser in core/signals.py.
• Set a real SECRET_KEY and move it to environment variables.
• Set DEBUG = False.
• Set a proper ALLOWED_HOSTS list.
• Configure production static/media serving.
• Review AI response parsing and add validation/error handling.
• Add logging instead of print statements.

Contributing

Contributions are welcome. A practical workflow:

1. Create a feature branch
2. Make focused changes
3. Run migrations/tests as needed
4. Open a pull request with a clear description of behavior changes