Files
rose-ash/account
giles 961067841e
All checks were successful
Build and Deploy / build-and-deploy (push) Successful in 3m14s
Tier 0 scalability: PgBouncer, Redis split, DB split, workers
T0.1: Separate redis-auth service (64mb, noeviction) for auth state
T0.2: Bump data Redis from 256mb to 1gb
T0.3: Per-app DATABASE_URL via PgBouncer to per-domain databases
T0.4: PgBouncer service (transaction mode, pool=20, max_conn=300);
      session.py pools reduced to 3+5 with timeout and recycle
T0.5: Hypercorn --workers 2 --keep-alive 75 on all 6 entrypoints

Deploy requires running split-databases.sh first to create per-domain
databases from the existing appdb.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-25 10:10:18 +00:00
..
2026-02-24 20:13:00 +00:00

Account App

User dashboard for the Rose Ash cooperative. Provides account management, newsletter preferences, and widget pages for tickets and bookings.

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/
  account/              #   Dashboard, newsletters, widget pages (tickets, bookings)
  auth/                 #   OAuth client routes + HTTP token exchange for non-coop clients
  fragments/            #   auth-menu fragment (sign-in button / user menu)
models/                 # Re-export stubs pointing to shared/models/
services/               # register_domain_services() — wires all domains
templates/              # Account-specific templates (override shared/)

Auth menu

Account serves the auth-menu fragment consumed by all other apps' headers. It renders either a sign-in button (anonymous) or the user's email with a dropdown (authenticated), for both desktop and mobile layouts.

OAuth token exchange

POST /auth/oauth/token provides HTTP-based token exchange for non-coop OAuth clients (e.g., Artdag).

Cross-domain communication

  • services.blog.* — post queries for page context
  • services.calendar.* — calendar/entry queries for bookings panel
  • services.cart.* — cart summary + orders for tickets panel

Fragments served

  • auth-menu — sign-in button or user email menu (desktop + mobile)