mirror of
https://github.com/koel/koel.git
synced 2026-04-26 09:15:59 +03:00
[PR #1004] [CLOSED] Improves cover handling by adding file name hashing. #1514
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#1514
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?
📋 Pull Request Information
Original PR: https://github.com/koel/koel/pull/1004
Author: @patric-eberle
Created: 6/22/2019
Status: ❌ Closed
Base:
master← Head:feature/hashed-filename-for-covers📝 Commits (1)
aca53bfFixes missing cover when toggling compilation state of a song.📊 Changes
1 file changed (+37 additions, -2 deletions)
View changed files
📝
app/Models/Album.php(+37 -2)📄 Description
When fixing the missing covers when toggling the compilation state of songs (#1003) I discovered, that a big pile of cover files where created during this process, because random file names are created. So even while the cover was always the same image, I had dozens of them in the end.
I decided to change the file name creation from random string to content based hash. Now covers can be reused. The downside is, that this method is a bit slower.
I choose sha256 because it seems to have the best speed/non conflict hash ratio.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.