mirror of
https://github.com/koel/koel.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #1379] Scan local folder removes s3-hosted records from the database #791
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#791
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 @sergiustheblack on GitHub (Nov 17, 2021).
Original GitHub issue: https://github.com/koel/koel/issues/1379
Describe the bug
When Scan operation is performed from web interface or
php artisan koel:syncfrom command line, all s3 records are removed from the database.Expected behavior
Records in MEDIA_PATH are resynced, but records previously added from s3 left in place.
Environment
@phanan commented on GitHub (Dec 5, 2021):
Hmm. I was always under the impression that one only uses either S3 or local and not both, but maybe this is an edge case I should cater to indeed.