starred/koel-koel

Fork 0

mirror of https://github.com/koel/koel.git synced 2026-04-25 08:46:00 +03:00

[GH-ISSUE #809] Duplicate entry bug and missing dependencies in preinstaller #570

New issue

Closed

opened 2026-02-26 02:33:35 +03:00 by kerem · 9 comments

kerem commented

2026-02-26 02:33:35 +03:00

Owner

Originally created by @JaneX8 on GitHub (Sep 26, 2018).
Original GitHub issue: https://github.com/koel/koel/issues/809

I noticed that the issues:

Have similar problems regarding the duplicate key. After struggling a long time I've finally managed to install Koel en wanted to start indexing. Then only one file was indexed and basically everything stopped working. I've tried it with and without docker, with PostgreSQL and MySQL, nothing seems to work. I wish it cost me an hour to get everything up and running but it costed me 10 so far and it's still not working. I'm thinking about writing the basic functionality myself now which would cost me the same time. But fact is Koel is looking nice and I would like to give it a try. It just doesn't work. How do I fix this?

The few rules at the site:

git clone https://github.com/phanan/koel
cd koel
composer install
php artisan koel:init
php artisan serve
Server started on http://localhost:8000/

Are misleading and too good to be true. I had to find and preinstall dependencies manually and edit PHP config and ENV files in order to work around the errors. Just to get a up-and-running interface. Any help? The duplicate key problem is now what I'm stuck on, just like the other issues are describing without a solution. I've tried truncating tables and removing one entry or file without luck too.

Originally created by @JaneX8 on GitHub (Sep 26, 2018). Original GitHub issue: https://github.com/koel/koel/issues/809 I noticed that the issues: - https://github.com/phanan/koel/issues/752 - https://github.com/phanan/koel/issues/705 - https://github.com/phanan/koel/issues/403 - https://github.com/phanan/koel/issues/255 Have similar problems regarding the duplicate key. After struggling a long time I've finally managed to install Koel en wanted to start indexing. Then only one file was indexed and basically everything stopped working. I've tried it with and without docker, with PostgreSQL and MySQL, nothing seems to work. I wish it cost me an hour to get everything up and running but it costed me 10 so far and it's still not working. I'm thinking about writing the basic functionality myself now which would cost me the same time. But fact is Koel is looking nice and I would like to give it a try. It just doesn't work. How do I fix this? The few rules at the site: git clone https://github.com/phanan/koel cd koel composer install php artisan koel:init php artisan serve Server started on http://localhost:8000/ Are misleading and too good to be true. I had to find and preinstall dependencies manually and edit PHP config and ENV files in order to work around the errors. Just to get a up-and-running interface. Any help? The duplicate key problem is now what I'm stuck on, just like the other issues are describing without a solution. _I've tried truncating tables and removing one entry or file without luck too._

kerem closed this issue

2026-02-26 02:33:35 +03:00

kerem commented

2026-02-26 02:33:35 +03:00

Author

Owner

@phanan commented on GitHub (Sep 26, 2018):

First thing first, the commands ("rules") are not "too good to be true." Granted, it's for development purpose (using PHP server) but below is my personal Koel installation/update script:

$ cat ./build-koel
#!/bin/bash

cd ~/domains/my.koel.domain
git pull
git submodule update --recursive --remote
composer install
php artisan koel:init

You see, all it takes is five statements (actually 4, as git submodule update --recursive --remote is only necessary because I'm on master branch).

Now to your struggling – I'm sorry it doesn't work right out of the box for you, but honestly I don't know where to start (to help you).

The duplicate key issue sounds like some weird encoding in your mp3 files, which I can't tell unless I have a copy of those files
The HTTPS issue (if you're having it) – I honestly believe this is a server config issue. I personally run Apache under a reverse-proxying nginx with SSL without any problem.
That you have to find and preinstall dependencies – if your environment is missing prerequisites or having them misconfigured, there's very little I can do. Btw you mentioned using docker – how come you still need to preinstall stuff?

@phanan commented on GitHub (Sep 26, 2018): First thing first, the commands ("rules") are not "too good to be true." Granted, it's for development purpose (using PHP server) but below is my personal Koel installation/update script: ```bash $ cat ./build-koel #!/bin/bash cd ~/domains/my.koel.domain git pull git submodule update --recursive --remote composer install php artisan koel:init ``` You see, all it takes is _five_ statements (actually 4, as `git submodule update --recursive --remote` is only necessary because I'm on `master` branch). Now to your struggling – I'm sorry it doesn't work right out of the box for you, but honestly I don't know where to start (to help you). * The duplicate key issue sounds like some weird encoding in your mp3 files, which I can't tell unless I have a copy of those files * The HTTPS issue (if you're having it) – I honestly believe this is a server config issue. I personally run Apache under a reverse-proxying nginx with SSL without any problem. * That you have to find and preinstall dependencies – if your environment is missing prerequisites or having them misconfigured, there's very little I can do. Btw you mentioned using docker – how come you still need to preinstall stuff?

kerem commented

2026-02-26 02:33:35 +03:00

Author

Owner

@JaneX8 commented on GitHub (Sep 27, 2018):

Thanks for your reply.

I've tried it with and without docker

The dependency problems where with the attempt without docker. If there is an encoding problem can we please fix that so it's rock-solid for all possible encoding?

@JaneX8 commented on GitHub (Sep 27, 2018): Thanks for your reply. > I've tried it with and without docker The dependency problems where with the attempt without docker. If there is an encoding problem can we please fix that so it's rock-solid for all possible encoding?

kerem commented

2026-02-26 02:33:35 +03:00

Author

Owner

@phanan commented on GitHub (Sep 27, 2018):

If there is an encoding problem can we please fix that so it's rock-solid for all possible encoding?

Again, I can not really fix a problem without knowing what the problem is i.e. without having the songs with funny encoding(s). And tbh, yours is a very edge case.

@phanan commented on GitHub (Sep 27, 2018): > If there is an encoding problem can we please fix that so it's rock-solid for all possible encoding? Again, I can not really fix a problem without knowing what the problem is i.e. without having the songs with funny encoding(s). And tbh, yours is a very edge case.

kerem commented

2026-02-26 02:33:35 +03:00

Author

Owner

@JaneX8 commented on GitHub (Sep 29, 2018):

I expect it has something to do with encoding stuff in the filenames/paths. Can that be? Letters like "äëöïüáéóíú".

@JaneX8 commented on GitHub (Sep 29, 2018): I expect it has something to do with encoding stuff in the filenames/paths. Can that be? Letters like "äëöïüáéóíú".

kerem commented

2026-02-26 02:33:35 +03:00

Author

Owner

@phanan commented on GitHub (Sep 29, 2018):

No, it’s the md3 tags for artist.

Aat2ya9873 notifications@github.com schrieb am So. 30. Sep. 2018 um 00:15:

I expect it has something to do with encoding stuff in the
filenames/paths. Can that be? Letters like "äëöïüáéóíú".

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/phanan/koel/issues/809#issuecomment-425678942, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AHrt0jk6TaGk3GLzI90wrCigk0DuRaCYks5uf_DlgaJpZM4W6FFG
.

@phanan commented on GitHub (Sep 29, 2018): No, it’s the md3 tags for artist. Aat2ya9873 <notifications@github.com> schrieb am So. 30. Sep. 2018 um 00:15: > I expect it has something to do with encoding stuff in the > filenames/paths. Can that be? Letters like "äëöïüáéóíú". > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <https://github.com/phanan/koel/issues/809#issuecomment-425678942>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/AHrt0jk6TaGk3GLzI90wrCigk0DuRaCYks5uf_DlgaJpZM4W6FFG> > . >

kerem commented

2026-02-26 02:33:35 +03:00

Author

Owner

@JaneX8 commented on GitHub (Oct 1, 2018):

So, can we make a fix that handles all possible characters in filenames/paths and md3 tags properly?

@JaneX8 commented on GitHub (Oct 1, 2018): So, can we make a fix that handles all possible characters in filenames/paths and md3 tags properly?

kerem commented

2026-02-26 02:33:35 +03:00

Author

Owner

@phanan commented on GitHub (Oct 1, 2018):

So, can we make a fix that handles all possible characters in filenames/paths and md3 tags properly?

I think we're going around in circle. You're asking me to "fix" something without giving any materials/evidence. Yes, I get it, it doesn't work for you, but that piece of information isn't helpful. You can at least provide me with the problematic files.

Again, I can not really fix a problem without knowing what the problem is i.e. without having the songs with funny encoding(s). And tbh, yours is a very edge case.

@phanan commented on GitHub (Oct 1, 2018): > So, can we make a fix that handles all possible characters in filenames/paths and md3 tags properly? I think we're going around in circle. You're asking me to "fix" something without giving any materials/evidence. Yes, I get it, it doesn't work for you, but that piece of information isn't helpful. You can at least provide me with the problematic files. > Again, I can not really fix a problem without knowing what the problem is i.e. without having the songs with funny encoding(s). And tbh, yours is a very edge case.

kerem commented

2026-02-26 02:33:35 +03:00

Author

Owner

@phanan commented on GitHub (Oct 1, 2018):

Also, you said "The dependency problems where[sic] with the attempt without docker." Doesn't that mean it's NOT a problem with Koel, and instead with your own server/environment, which in turn renders a good part of this issue report an unconstructive rant?

@phanan commented on GitHub (Oct 1, 2018): Also, you said "The dependency problems where[sic] with the attempt without docker." Doesn't that mean it's NOT a problem with Koel, and instead with _your own_ server/environment, which in turn renders a good part of this issue report an unconstructive rant?

kerem commented

2026-02-26 02:33:35 +03:00

Author

Owner

@phanan commented on GitHub (Oct 1, 2018):

I'm closing this issue because it's pretty misleading. If you want to report the actual issue with encoding, please open another one and provide more information i.e. the files with errors.

@phanan commented on GitHub (Oct 1, 2018): I'm closing this issue because it's pretty misleading. If you want to report the actual issue with encoding, please open another one and provide more information i.e. the files with errors.

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#570

No description provided.

Rows
Columns