Pizza Logs

Pizza Logs turns Wrath of the Lich King combat logs into readable raid sessions, boss pulls, DPS/HPS records, player profiles, gear snapshots, and progression summaries. It is built for PizzaWarriors on Warmane Lordaeron, while remaining useful for compatible WotLK 3.3.5a logs.

The Molten Charcoal identity pairs warm charcoal surfaces, ember-orange accents and cream text with the original Pizza Warriors crest. The site, install icons and shared-link previews use the same branding.

Open the live app · Read the docs · Report a bug · Report a vulnerability privately

The 1.0.0 release contract defines the stable canonical product: supported report links, bounded uploads and documented parser metrics. It records compatibility commitments and known limits, including incomplete full UwU parity, reupload after interruption and owner-deferred provider recovery. The product version is independent of parser version 1.1.1; the release record and deployment checks establish which revision is live.

What It Does

• Streams .txt, .log, or .zip uploads with live progress and bounded server-side validation.
• Detects boss encounters even when Warmane omits useful encounter markers.
• Preserves Skada-WoTLK damage/healing primitives. UwU reference comparisons and known differences are tracked in the parity contract; broad equivalence is not claimed.
• Reports raid sessions, boss attempts, target damage, healing, absorbs, deaths, auras, consumables, power gains, specs, roles, and pets.
• Offers All Boss Attempts and Successful Boss Fights views with matching player totals, target damage and rates; full-session trash and downtime remain a separate view.
• Tracks all-time records, weekly results, boss history, and player performance.
• Filters raids, players, boss history, weekly results and leaderboards by realm, with shareable URLs and realm-aware player search.
• Adds first-party Warmane roster and gear lookups with durable cached fallback.
• Protects diagnostics, cleanup, import, and refresh controls behind server-side admin authentication.
• Runs as separate Next.js and FastAPI services backed by PostgreSQL on Railway.

How It Fits Together

flowchart LR
  Browser["Browser"] -->|"SSE upload and reports"| Web["Next.js web service"]
  Web -->|"bounded byte stream"| Parser["FastAPI parser service"]
  Parser -->|"validated analytics"| Web
  Web <--> Database["PostgreSQL via Prisma"]
  Web -->|"best-effort server fetch"| Warmane["Warmane Armory/CDN"]
  Railway["Railway main deployment"] --> Web
  Railway --> Parser

The browser never receives database credentials, parser filesystem paths, or the admin secret. Raw uploads are streamed through the web service, validated by the parser, reduced to structured analytics, and removed from parser temporary storage after processing.

Stack

Layer	Technology
Web	Next.js 16.3, React 19.2, Node.js 24
Language	TypeScript 7 native CLI plus TypeScript 6 ecosystem check
UI	Tailwind CSS 4, Recharts 3
Data	PostgreSQL, Prisma 7
Parser	Python 3.14, FastAPI, Pydantic
Hosting	Railway, separate web and parser services
Security automation	CodeQL, Dependabot, dependency review, pinned Actions

Quick Start

Prerequisites:

• Node.js 24.x and npm 11+
• Python 3.14
• PostgreSQL 16, or Docker Desktop

Install the web dependencies and create local configuration:

npm ci --legacy-peer-deps
cp .env.example .env.local
npm run db:generate
npx prisma migrate deploy
npm run db:seed

Install the parser from the reviewed, hash-locked dependency set:

python -m venv parser/.venv

Install dependencies with the virtual environment's interpreter:

# Windows
.\parser\.venv\Scripts\python.exe -m pip install --require-hashes -r .\parser\requirements-dev.lock

# macOS/Linux
parser/.venv/bin/python -m pip install --require-hashes -r parser/requirements-dev.lock

Start the parser and web app in separate terminals:

# Windows
.\parser\.venv\Scripts\python.exe .\parser\main.py

# macOS/Linux
parser/.venv/bin/python parser/main.py

# Either platform, in the web-app terminal
npm run dev

Then open http://localhost:3000. A local production-style stack is also available:

Set a random ADMIN_SECRET of at least 32 characters in .env.local before starting Compose.

docker compose --env-file .env.local up --build

See development setup for database, item metadata, Windows launchers, and environment details.

Configuration

Variable	Required	Purpose
DATABASE_URL	Yes	PostgreSQL connection used by Prisma
PARSER_SERVICE_URL	Yes	Internal FastAPI service base URL
ADMIN_SECRET	Yes for admin	Server-only signing/encryption key, at least 32 random characters; never a browser login credential
ADMIN_AUTH_URL	Yes for admin	Exact public HTTPS origin; loopback HTTP is supported for isolated development
ADMIN_COOKIE_SECURE	Local HTTP only	Set false only for local production-mode HTTP
ENABLE_LEGACY_PARSER_ROUTES	No	Local parser compatibility escape hatch; disabled by default

Never commit local .env files. The checked-in .env.example contains placeholders only.

Admin access uses an operator-provisioned account, an authenticator code and revocable sessions. Follow admin account setup and recovery before enabling it.

Validation

The complete web/TypeScript gate is:

npm run check:pr

The parser gate is:

cd parser
pytest tests/ -v

Parser behavior changes require focused pytest or fixture coverage. parser/tests/fixtures/README.md explains the fixture format. Useful additional checks are documented in testing.

Parser Guarantees

Parser correctness is the product. The detailed contract lives in docs/parser-contract.md; the short version is:

• Skada-WoTLK defines the supported damage/healing event sets and effective-healing primitive.
• Headline outgoing damage and damage taken use raw combat-log amounts; useful/effective damage is separate.
• Absorbs stay separate from effective healing, with an explicitly labeled healing-plus-absorbs comparison view.
• Encounter windows end on boss-destination activity, with boss death as the kill endpoint.
• Difficulty, pet ownership, and absorb ownership remain unknown/unattributed when evidence conflicts or is missing.
• Gunship, Lich King scripted phases, Warmane GUIDs, back-to-back pulls, and pet ownership are regression tested.

Public Routes

Route	Purpose
/	Upload and project summary
/raids	Public raid history
/raids/[report]/sessions/[date]	Canonical dated raid session
/encounters/[id]	Boss-pull breakdown
/leaderboards	Top-three all-time average DPS/HPS across logged boss attempts and per-boss personal-best kill records
/players and /players/[name]	Player directory and profiles
/guild-roster	Cached PizzaWarriors roster
/weekly	Weekly kills and performance
/bosses and /bosses/[slug]	Boss-specific history and rankings
/admin	Authenticated diagnostics and maintenance

Legacy numeric/CUID upload links redirect to canonical public raid URLs where a public report exists. The retired userscript update URLs remain inert only to safely disable old installations.

Documentation

• Documentation index
• Architecture
• Upload protocol
• Parser contract
• UwU analytical parity
• Security policy and threat model
• Railway runbook
• Contribution workflow
• Changelog
• Privacy

Contributing

Use a short-lived branch from current origin/main, keep changes scoped, run the relevant gates, and open a pull request. Do not push directly to main. Parser, schema, upload, admin, security, and deployment changes need especially clear evidence.

See CONTRIBUTING.md and AGENTS.md.

Privacy, Security, and License

Raid reports contain public in-game character names and performance data. Pizza Logs has no end-user account system, advertising SDK, or payment flow. Read PRIVACY.md for collection and retention details.

Please report vulnerabilities through a private GitHub security advisory, not a public issue. Security controls and known residual risks are documented in SECURITY.md.

The project is released under the MIT License. World of Warcraft and related marks are property of Blizzard Entertainment; Warmane and other referenced services are independent third parties. See THIRD_PARTY_NOTICES.md.