At the moment the playlist definitions are entirely contained within the code.
The env variables let me tune how many of each component are put into the playlist, and which plex servers etc but it involves coding effort to change or build a new playlist.
Ultimately I'd like to build in some kind of markup language (YAML, configParser, etc) that would let me define playlists.
eg something like this would let me define (somewhat) arbitrary playlists in a config file:
5-star-lru:
- source: music-section
- filter:
-- sort: lastPlayed ASC
-- rating: 5
-- select: 20
- select: random 10
- publish: False
4-star-lru:
- source: music-section
- filter:
-- sort: lastPlayed ASC
-- rating: 4
-- select: 50
- select: random 20
- publish: False
hot-mix:
- source: [4-star-lru, 5-star-lru]
- select: random 50
- publish: True
At the moment the playlist definitions are entirely contained within the code.
The env variables let me tune how many of each component are put into the playlist, and which plex servers etc but it involves coding effort to change or build a new playlist.
Ultimately I'd like to build in some kind of markup language (YAML, configParser, etc) that would let me define playlists.
eg something like this would let me define (somewhat) arbitrary playlists in a config file: