The evolution of a Django Website into a radio automation back-end
summary
A website that showed a free radio schedule becomes a radio automation back-end that serves the schedule over a REST API and drives playout. It uses Django and Django REST Framework, runs in Docker compose, and models shows, schedules and time slots; the suite splits into steering, tank, engine plus a dashboard and web play components. It handles about 120 pre-recorded shows, supports 31 recurrence rules, implements four collision types with concrete resolution strategies, and exposes JSON APIs for create/replace workflows.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 2:11Free radio landscape
- 4:02Radio automation evolution
- 6:33AA project architecture
- 8:04Core AA components
- 10:15Program modeling
- 11:42Recurrence rules
- 13:32Scheduling collisions
- 17:53Collision resolution demo
- 20:54Django to REST improvements
- 22:19AA team
- 23:25Future plans
- 24:34Closing
related talks
22mThe evolution of a Website into a radio automation back-end.
23mThree Django Apps in a Trenchcoat: Writing an event management website with not a lot of time
26mDjango at
29mHow Django helped us make a better conference website
42mDjangular
26mA Fireside Chat
26mDjango, REST and OpenAPI - a gentle introduction
42mA Python-Driven Web App Framework with Django, Channels, and React