mirror of
https://github.com/koel/koel.git
synced 2026-04-25 16:56:02 +03:00
[GH-ISSUE #1214] Sync Library in Background from UI #690
Labels
No labels
Authentication
Dependencies
Documentation
Feature Request
Flac
Help Wanted
Installation/Setup
Integration
Mobile
PR Welcome
Pending Release
Performance
Playlist
S3
Search
Sync
[Pri] Low
[Pri] Normal
[Status] Keep Open
[Status] Needs Author Reply
[Status] Needs Review
[Status] Stale
[Status] Will Implement
[Type] Blessed
[Type] Bug
[Type] Duplicate
[Type] Enhancement
[Type] Help Request
[Type] Question
[Type] Task
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/koel-koel#690
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
@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.
@BrookeDot commented on GitHub (Apr 22, 2020):
I agree with that, especially as you can have it run as a
crontask in the background.@phanan commented on GitHub (May 5, 2020):
Closing as I don't plan to support this in the near future.