Files
mono/events
giles 22802bd36b Send all responses as sexp wire format with client-side rendering
- Server sends sexp source text, client (sexp.js) renders everything
- SexpExpr marker class for nested sexp composition in serialize()
- sexp_page() HTML shell with data-mount="body" for full page loads
- sexp_response() returns text/sexp for OOB/partial responses
- ~app-body layout component replaces ~app-layout (no raw!)
- ~rich-text is the only component using raw! (for CMS HTML content)
- Fragment endpoints return text/sexp, auto-wrapped in SexpExpr
- All _*_html() helpers converted to _*_sexp() returning sexp source
- Head auto-hoist: sexp.js moves meta/title/link/script[ld+json]
  from rendered body to document.head automatically
- Unknown components render warning box instead of crashing page
- Component kwargs preserve AST for lazy rendering (fixes <> in kwargs)
- Fix unterminated paren in events/sexp/tickets.sexpr

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-01 09:45:07 +00:00
..
2026-02-24 20:13:00 +00:00

Events App

Calendar and event booking service for the Rose Ash cooperative platform. Manages calendars, time slots, calendar entries (bookings), tickets, and ticket types.

Structure

app.py                  # Application factory (create_base_app + blueprints)
path_setup.py           # Adds project root + app dir to sys.path
entrypoint.sh           # Container entrypoint (Redis flush, start)
bp/
  calendars/            #   Calendar listing
  calendar/             #   Single calendar view and admin
  calendar_entries/     #   Calendar entries listing
  calendar_entry/       #   Single entry view and admin
  day/                  #   Day view and admin
  slots/                #   Slot listing
  slot/                 #   Single slot management
  ticket_types/         #   Ticket type listing
  ticket_type/          #   Single ticket type management
  tickets/              #   Ticket listing
  ticket_admin/         #   Ticket administration
  markets/              #   Page-scoped marketplace views
  payments/             #   Payment-related views
  fragments/            #   container-nav, container-cards fragments
models/                 # Re-export stubs (Calendar, CalendarEntry, Ticket, etc.)
services/               # register_domain_services() — wires calendar + market + cart
templates/              # Events-specific templates (override shared/)

Models

All events-domain models live in shared/models/:

Model Description
Calendar Container for entries, scoped to a page via container_type + container_id
CalendarEntry A bookable event/time slot with state (pending/ordered/provisional) and cost
CalendarSlot Recurring time bands (day-of-week + time range) within a calendar
TicketType Named ticket categories with price and count
Ticket Individual ticket with unique code, state, and order_id (plain integer, no FK)
CalendarEntryPost Junction linking entries to content via content_type + content_id

order_id on CalendarEntry and Ticket is a plain integer column — no FK constraint to the orders table. The cart app writes these values via service calls, not directly.

Cross-domain communication

  • services.market.* — marketplace queries for page views
  • services.cart.* — cart summary for context processor
  • services.federation.* — AP publishing for new entries

Fragments served

  • container-nav — calendar entries + links for blog sidebar
  • container-cards — event cards for blog listing pages