mirror of
https://github.com/koel/koel.git
synced 2026-04-25 16:56:02 +03:00
[GH-ISSUE #1681] S3 files not all synced #923
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#923
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 @Kinzi on GitHub (May 17, 2023).
Original GitHub issue: https://github.com/koel/koel/issues/1681
Got the S3 integration up and running but it turns out not all files have been synced into Koel.
Some albums are missing completely, other's don't have all songs in them.
Is there a way to re-sync the full bucket somehow?
@dmuiX commented on GitHub (Nov 6, 2023):
you can always do
docker exec --user www-data -it <container-name> php artisan koel:sync -vWith the v in the end it shows you want went wrong. maybe you get similiar results as I am: https://github.com/koel/koel/issues/1722
if installed locally i think you just do
php artisan koel:sync -v, but I am not sure.https://docs.koel.dev/#music-discovery
@phanan commented on GitHub (Jul 10, 2024):
A bit late, but Koel Plus now has full support for S3 as a storage driver.