- Dockerfile: replace single runner stage with web + scraper named targets - web: Next.js standalone only — no playwright, tsx, or scripts - scraper: scripts/lib/node_modules/playwright only — no Next.js output - docker-compose.yml: each service pulls its dedicated image tag - .gitea/workflows/deploy.yml: build both targets on push to main - lib/db.ts: STALE_AFTER_MS reads PARK_HOURS_STALENESS_HOURS env var (default 72h) - lib/park-meta.ts: COASTER_STALE_MS reads COASTER_STALENESS_HOURS env var (default 720h) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Thoosie Calendar
A week-by-week calendar showing operating hours for all Six Flags Entertainment Group theme parks — including the former Cedar Fair parks. Data is scraped from the Six Flags internal API and stored locally in SQLite. Click any park to see its full month calendar and live ride status with current wait times.
Parks
24 theme parks across the US, Canada, and Mexico, grouped by region:
| Region | Parks |
|---|---|
| Northeast | Great Adventure (NJ), New England (MA), Great Escape (NY), Darien Lake (NY), Dorney Park (PA), Canada's Wonderland (ON) |
| Southeast | Over Georgia, Carowinds (NC), Kings Dominion (VA) |
| Midwest | Great America (IL), St. Louis (MO), Cedar Point (OH), Kings Island (OH), Valleyfair (MN), Worlds of Fun (MO), Michigan's Adventure (MI) |
| Texas & South | Over Texas, Fiesta Texas (TX), Frontier City (OK) |
| West & International | Magic Mountain (CA), Discovery Kingdom (CA), Knott's Berry Farm (CA), California's Great America (CA), Mexico |
Tech Stack
- Next.js 15 — App Router, Server Components, standalone output
- Tailwind CSS v4 —
@theme {}CSS variables, no config file - SQLite via
better-sqlite3— persisted in/app/data/parks.db - Playwright — one-time headless browser run to discover each park's internal API ID
- Six Flags CloudFront API —
https://d18car1k0ff81h.cloudfront.net/operating-hours/park/{id}?date=YYYYMM - Queue-Times.com API — live ride open/closed status and wait times, updated every 5 minutes
Ride Status
The park detail page shows ride open/closed status using a two-tier approach:
-
Live data (Queue-Times.com) — when a park is operating, ride status and wait times are fetched from the Queue-Times.com API and cached for 5 minutes. All 24 parks are mapped. Displays a Live badge with per-ride wait times.
-
Schedule fallback (Six Flags API) — the Six Flags operating-hours API drops the current day from its response once a park opens. When Queue-Times data is unavailable, the app falls back to the nearest upcoming date from the Six Flags schedule API as an approximation.
Roller Coaster Filter
When live data is shown, a Coasters only toggle appears if roller coaster data has been populated for that park. Coaster lists are sourced from RCDB and stored in data/park-meta.json. To populate them:
- Open
data/park-meta.jsonand setrcdb_idfor each park to the numeric RCDB park ID (visible in the URL:https://rcdb.com/4529.htm→4529). - Run
npm run scrape— coaster lists are fetched from RCDB and stored in the JSON file. They refresh automatically every 30 days on subsequent scrapes.
Local Development
Prerequisites: Node.js 22+, npm
npm install
npx playwright install chromium
Seed the database
Run once to discover each park's internal API ID (opens a headless browser per park):
npm run discover
Scrape operating hours for the full year:
npm run scrape
Force a full re-scrape (ignores the 7-day staleness window):
npm run scrape:force
Debug a specific park + date
Inspect raw API data and parsed output for any park and date:
npm run debug -- --park kingsisland --date 2026-06-15
Output is printed to the terminal and saved to debug/{parkId}_{date}.txt.
Run the dev server
npm run dev
Open http://localhost:3000. Navigate weeks with the ← / → buttons, or pass ?week=YYYY-MM-DD directly. Click any park name to open its detail page.
Deployment
The app uses Next.js standalone output. The SQLite database is stored in a Docker volume at /app/data.
docker compose up -d
Seed the database inside the container
The production image includes Playwright and Chromium, so discovery and scraping run directly against the container's volume:
docker compose exec web npm run discover
docker compose exec web npm run scrape
Or as a one-off against the named volume:
docker run --rm -v sixflagssupercalendar_park_data:/app/data \
gitea.thewrightserver.net/josh/sixflagssupercalendar:latest \
npm run scrape
Data Refresh
The scraper skips any park + month already scraped within the last 72 hours. The nightly Docker scraper service handles this automatically. Parks or months not yet in the database show a — placeholder; parks with no open days in the displayed week are hidden from the calendar automatically.
Roller coaster lists (from RCDB) are refreshed every 30 days on each npm run scrape run, for parks with a configured rcdb_id.