How dev-casolari/next-set works
NextSet lets visitors choose a random DJ set from either the full or curated Google Sheet catalog, filter the loaded sets, and play a selection in YouTube’s official embedded player. The request path reads and validates sheet data before returning a catalog; browser selection and playback then operate on that loaded catalog. The graph retains the documented filter and catalog-switch stages. Source excerpts show the main calls; the HTML structure and some UI wiring were not sampled, so those connections are omitted where unsupported.
Main entry points: catalog.py Sheet reader · app.js Catalog UI · main.py HTTP routes · player.js Player controller
Components 11
Catalog service
- App startup
app/__main__.py - Settings
app/config.py - HTTP routes
app/main.py - Sheet reader
app/catalog.py - Set models
app/models.py
Browser experience
- Catalog UI
app/static/app.js - Filter and select
app/static/selection.js
Video playback
- Player controller
app/static/player.js
Other components
- Visitor
- Google Sheets
- YouTube player
Connections 12
- Visitor → Catalog UI: chooses filters
README.md - Catalog UI → HTTP routes: fetches catalog
app/static/app.js - HTTP routes → Sheet reader: requests catalog
app/main.py - Sheet reader → Settings: uses configuration
app/catalog.py - Sheet reader → Google Sheets: reads worksheet
app/catalog.py - Sheet reader → Set models: constructs sets
app/catalog.py - HTTP routes → Set models: returns response model
app/main.py - Catalog UI → Filter and select: selects from catalog
app/static/app.js - Catalog UI → Player controller: replaces player
app/static/app.js - Player controller → YouTube player: loads and cues
app/static/player.js - App startup → HTTP routes: starts application
app/__main__.py - Visitor → YouTube player: presses Play
README.md