[GH-ISSUE #1214] Sync Library in Background from UI #690

Closed
opened 2026-02-26 02:33:58 +03:00 by kerem · 3 comments
Owner

Originally created by @DDriggs00 on GitHub (Apr 17, 2020).
Original GitHub issue: https://github.com/koel/koel/issues/1214

Description
While it is possible to import large libraries via both the web interface and the terminal, the web interface becomes unusable while the library is importing, which is not a convenient when importing large libraries (mine is 23k files) takes a very long time.

Example
If implemented, clicking the sync button would start the sync in the background, allowing use of the interface while the library is importing.

Originally created by @DDriggs00 on GitHub (Apr 17, 2020). Original GitHub issue: https://github.com/koel/koel/issues/1214 **Description** While it is possible to import large libraries via both the web interface and the terminal, the web interface becomes unusable while the library is importing, which is not a convenient when importing large libraries (mine is 23k files) takes a very long time. **Example** If implemented, clicking the sync button would start the sync in the background, allowing use of the interface while the library is importing.
kerem 2026-02-26 02:33:58 +03:00
Author
Owner

@phanan commented on GitHub (Apr 21, 2020):

It's a nice idea, but in practice, it might not be that simple. What if the syncing process removes those songs being displayed (and interacted with) on the web interface? How about timeouts? This can lead to weird behaviors and errors.

IMO if you have a large library, it's best to use the command line. After all, the web isn't designed for such long tasks.

<!-- gh-comment-id:617437709 --> @phanan commented on GitHub (Apr 21, 2020): It's a nice idea, but in practice, it might not be that simple. What if the syncing process removes those songs being displayed (and interacted with) on the web interface? How about timeouts? This can lead to weird behaviors and errors. IMO if you have a large library, it's best to use the command line. After all, the web isn't designed for such long tasks.
Author
Owner

@BrookeDot commented on GitHub (Apr 22, 2020):

IMO if you have a large library, it's best to use the command line. After all, the web isn't designed for such long tasks.

I agree with that, especially as you can have it run as a cron task in the background.

<!-- gh-comment-id:617558417 --> @BrookeDot commented on GitHub (Apr 22, 2020): > IMO if you have a large library, it's best to use the command line. After all, the web isn't designed for such long tasks. I agree with that, especially as you can have it run as a `cron` task in the background.
Author
Owner

@phanan commented on GitHub (May 5, 2020):

Closing as I don't plan to support this in the near future.

<!-- gh-comment-id:623886943 --> @phanan commented on GitHub (May 5, 2020): Closing as I don't plan to support this in the near future.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/koel-koel#690
No description provided.