The evolution of a Website into a radio automation back-end.
summary
A website that displayed a free‑radio schedule becomes a distributed automation back end: a Django app called steering acts as the source of truth and steering as OpenID Connect provider, tank stores playlists and media, and the engine uses Liquidsoap with silence detection and optional recording. The system implements 31 recurrence rules (daily, weekly, biweekly, monthly variants) and a deterministic collision resolver that returns a 409 with a collision hash and named solutions like theirs or ours so scheduling via REST API works in production.
AI-written summary · about
chapters (10)
- 0:00Introduction and background
- 3:25Challenges with commercial software
- 5:36Need for a new open-source solution
- 7:00Aura’s modular architecture
- 9:12Program modeling with shows
- 10:39Recurrence rules and scheduling
- 12:06Time slot collision detection
- 16:04Demo of collision resolution
- 19:11Current team and contributors
- 20:14Future plans and call to action
related talks
26mThe evolution of a Django Website into a radio automation back-end
23mThree Django Apps in a Trenchcoat: Writing an event management website with not a lot of time
29mHow Django helped us make a better conference website
26mDjango at
53mDjango: a Data Shovel With a Future
33mKEYNOTE: Making Movies With Web Applications
52mChallenges in developing a large Django site
18mBuilding theatlantic.com homepage’s WYSIWYG admin with...