[GH-ISSUE #1379] Scan local folder removes s3-hosted records from the database #791

Closed
opened 2026-02-26 02:34:17 +03:00 by kerem · 1 comment
Owner

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:sync from 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

  • Koel version: v5.1.8
  • OS: official Koel docker image
  • Database: PostgreSQL 13.4
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:sync` from 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** - Koel version: v5.1.8 - OS: official Koel docker image - Database: PostgreSQL 13.4
kerem closed this issue 2026-02-26 02:34:17 +03:00
Author
Owner

@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.

<!-- gh-comment-id:986261746 --> @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.
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#791
No description provided.