Persistently Store Channel Queue to Database. #82

New issue

Closed

opened 2025-01-02 07:17:57 -05:00 by rainbownapkin · 7 comments

rainbownapkin commented

2025-01-02 07:17:57 -05:00

(Migrated from gitlab.com)

Keep a copy of the channel queue to keep queues over server-restarts.

Queue should be saved periodically instead of on modification for performance reasons.

Items that have not yet played or are currently playing should be held in the 'schedule' sub-doc of channel.

Old items should be held in the 'history' sub-doc

Keep a copy of the channel queue to keep queues over server-restarts. Queue should be saved periodically instead of on modification for performance reasons. Items that have not yet played or are currently playing should be held in the 'schedule' sub-doc of channel. Old items should be held in the 'history' sub-doc

rainbownapkin commented

2025-01-02 07:17:57 -05:00

(Migrated from gitlab.com)

added #76 as parent issue

rainbownapkin commented

2025-01-02 07:19:03 -05:00

(Migrated from gitlab.com)

changed title from Persistently {-s-}tore {-c-}hannel {-q-}ueue to {-d-}atabase. to Persistently {+S+}tore {+C+}hannel {+Q+}ueue to {+D+}atabase.

changed title from **Persistently {-s-}tore {-c-}hannel {-q-}ueue to {-d-}atabase.** to **Persistently {+S+}tore {+C+}hannel {+Q+}ueue to {+D+}atabase.**

rainbownapkin commented

2025-01-02 07:19:04 -05:00

(Migrated from gitlab.com)

changed the description

rainbownapkin commented

2025-01-02 07:21:38 -05:00

(Migrated from gitlab.com)

changed the description

rainbownapkin commented

2025-02-09 00:55:00 -05:00

(Migrated from gitlab.com)

changed the description