XTS

eXtensible Ticketing System

This page is a stub. I intend to document as much of the ticketing system as possible but keep forgetting things that I want to write about. Until it's completed, here's a list of sections that I intend to write under. This article is currently aimed at people who want to maintain the source code, NOT people who want to learn how to sell tickets.

• History / Motivation
• Things you should know before you start
  • Terminology
    • "Reserved" vs. "Booked".
    • "Holding" tickets.
  • Principles
    • Portability (OS Transparency)
    • Accessibility (Network Transparency)
    • Extensibility
    • Readability
    • Simplicity (Minimum Complexity in the Layers that Matter)
    • High-Level Scripting
• Parts of the system
  • Database
    • Scheduled Database Backup
  • Ticket Server
    • Web.py
    • API
    • Security
  • Print Server
    • API
    • Making new ticket layouts
    • Changing the ticket logo
  • Static Server
    • Apache 2.2
  • Javascript Client
    • Ami
    • Snewts
    • Prism
  • Reporting
    • XSLT
  • HTTPProxy
  • Startup - Windows Services
    • JSWrapper
• Making Improvements - A HOWTO
  • Known Issues
    • Grokking the Source
  • Familiarisation
  • Tools You Must Use
    • Firebug
    • IPython
  • Safe and Unsafe
  • Versioning

Parts of the System

Database

XTS uses a MySQL database. It should be very easy to port XTS to other databases, most access is abstracted through web.py but there may be some specific report-generating SQL queries that are specific to MySQL in the XTS source. See #data.py for more info.

Ticket Server

Source

snewts.py

About snewts.py

logic.py

About logic.py

data.py

About data.py