mirror of
https://github.com/koel/koel.git
synced 2026-04-25 08:46:00 +03:00
[GH-ISSUE #1305] Support Subdirectory Installation #754
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#754
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 @sergiud on GitHub (Apr 13, 2021).
Original GitHub issue: https://github.com/koel/koel/issues/1305
Describe the bug
I'm running Koel at a non-root location
http://myurl/sub/. This mostly works as expected. However, very few links still point tohttp://myurl/instead ofhttp://myurl/sub/. Specifically,jsandimgobjects are expected to be in the root athttp://myurl/js/andhttp://myurl/img/instead ofhttp://myurl/sub/js/andhttp://myurl/sub/img//subpart. User profile details can still be accessed under Manage/Users.To reproduce
Install Koel in a subfolder.
Expected behavior
All links are correct and subfolder location is not ignored.
Environment
@phanan commented on GitHub (Apr 16, 2021):
Koel doesn't officially support subfolder installations though.
@sergiud commented on GitHub (Apr 16, 2021):
Thanks for the feedback.
Possibly I missed this information, but I could not find this restriction in the documentation. According to your previous comment and PR #673 non-root installations are expected to work.
Since these are minor issues, it would be nice if these remaining problems could be resolved as well.
@sergiud commented on GitHub (Apr 16, 2021):
@fieteboerner Do you happen to know why the links in the header and the footer still make requests to the root URL? All other links seem to work.
@phanan commented on GitHub (Apr 16, 2021):
Sorry for the confusion. You're right, there was a PR to support this but apparently, it doesn't work so well now. I'm open to a fix :)
@sergiud commented on GitHub (Apr 16, 2021):
Great, thank you!
@Jodge65 commented on GitHub (Oct 18, 2021):
I'm very interested in this issue, because it's seems to be linked to reverse proxy error.
I'm not hundred percent sure that the following information are relevant for sub-directory problem.
I do some research, and i found the following information :

The player cannot load because of a missing dot in the src
Those lines are generated by an app.js script:

The variable o.p is "/" instead of "./", i try to edit on the go, and it was working.
Unfortunately, i'm not familiar enough with js/ts to locate the part of code that generated this file
@sergiud commented on GitHub (Oct 19, 2021):
You don't actually need a reverse proxy. For reference, this is how I integrated Koel into an Nginx server instance:
You would include the conf in your
nginx.confand then access Koel under<URL>/music.@sergiud commented on GitHub (Sep 23, 2022):
As of Koel 6.2.0, subdirectory installation is still not fully supported. Why close the issue?
@PermaFreez commented on GitHub (Feb 24, 2023):
I would like to see this resolved too.