a proof of concept for self hosting streaming radio.
This is the user facing stream interface. It's a front end that can play the stream has volume controls. It also provides an overlay that can display what is scheduled on the stream for today. Finally it has a simple websocket chat, along with a active user list.
The admin app provides a library to upload music files to. It contains a MP3 metadata editor, so you can control the artist/album/song fields of your music. Note: Files uploaded to the root directory will be used for the random unscheduled playlists. Files place in a folder are only accessible for schedules.
The app allows you to schedule playlist to run during specific blocks of time. Schedules run once a week. You can provide a name, description, and a designated start time. Then you can select any of the files you have uploaded to the library using the multiselect provided. The length of the schedule is determined by the length of the files added to the playlist.
You can create, update, and delete schedules as needed.
before anything else, you'll need FFMPEG locally. if you don't already, run brew install ffmpeg to install it locally.
you may run into a somewhat-common issue of the install failing when building symlinks, which is fixed in this GitHub thread.
in the client, server, admin, and stream directories, you'll find .env.example files. create a new .env file for each directory and copy the content of the .env.example.
to populate your radio stream, mkdir stream/assets/audio and fill the directory with mp3 files of your choosing.
the VIDEO_PATH directory is where you can store mp4 files that will be used as the video portion of the stream. each song will randomly select one video file in this directory for it's duration.
the portion of the app runs the RTMP server, chat websockets, and API services for osr. it's currently configured to run on a sqlite database.
cd server
npm install
./node_modules/.bin/knex migrate:latest
node index.js
this is the ffmpeg process, it connects to the sqlite db to configure it's currently playing song and then broadcasts it's stream to the RMTP server. it can be started and stopped using the admin app.
the front end of osr. preview available here
cd client
npm install
npm start
The admin front end of osr. It can be accessed at /admin. This app provides a web interface for managing the stream. It allows you to:
- create schedules
- start/stop the stream
- upload and delete songs
- manage uploaded mp3s metadata