mirror of
https://github.com/koel/koel.git
synced 2026-04-25 16:56:02 +03:00
[GH-ISSUE #529] Support for non-root folder installation #374
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#374
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 @ElectronicWar on GitHub (Jan 31, 2017).
Original GitHub issue: https://github.com/koel/koel/issues/529
Freshly installed Koel v3.5.4 on Debian Stretch, Node 6.9.4, yarn v0.19.1, PHP 7.0.14, MariaDB 10, Nginx 1.10.2
I've edited
.envand setAPP_URL=https://example.org/koel/I haven't seen anything else that looks like a suitable option.
The Koel page loads, but most resources are missing and the api is using the wrong url as well.
This results in non-working login and a bleak login page.
Some example request:
https://example.com/public/img/logo.svginstead ofhttps://example.com/koel/public/img/logo.svgApi is called from
https://example.org/api/meinstead ofhttps://example.org/koel/api/meIs it even supported to be run in a subfolder?
@phanan commented on GitHub (Feb 1, 2017):
Sorry, but Koel doesn't support subfolder installation.
@paulklemm commented on GitHub (Feb 1, 2017):
Are there plans for this on the projects road map? This would be very useful for me.
@phanan commented on GitHub (Feb 1, 2017):
Re-opening so that I/contributors can revisit this later.
@katlyn commented on GitHub (Feb 11, 2017):
This is probably a little hacky, but I have run Koel in a sub folder by putting the installation in that folder on a web server. I am not sure if this works for the current version, but after I did
composer installand that stuff it worked in the sub folder.For example, if you want it to be accessed at
example.com/koel, install Koel inPUBLIC_DIR/koel.@ElectronicWar commented on GitHub (Feb 11, 2017):
Didn't work for me as mentioned above, the api would still make requests ignoring the subfolder.
@katlyn commented on GitHub (Feb 11, 2017):
Just tried it with the current version, and it looks like @ElectronicWar is right. I don't know which version I was using at the time, or if if I changed any files, but thought it was worth a try.
@phanan commented on GitHub (Dec 4, 2017):
Non-root installations should be OK now with the great PR from @fieteboerner (thanks again!)
@tlaguz commented on GitHub (Oct 5, 2020):
It looks like it's broken in v4.4.0. I fixed it like this: bf6e7609aad229d43f5b09e82583c8fc729d3eab
After changes:
./artisan koel:init