mirror of
https://github.com/koel/koel.git
synced 2026-04-25 16:56:02 +03:00
[GH-ISSUE #215] Can this run on apache? #154
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#154
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 @ArjonBu on GitHub (Feb 1, 2016).
Original GitHub issue: https://github.com/koel/koel/issues/215
I want to run your application on apache. Is this possible? If yes, what is the vhost config?
@JoseCage commented on GitHub (Feb 1, 2016):
@Arjoni I believe that it is possible in this case putting the public folder on your host configuration
@zazatek commented on GitHub (Feb 1, 2016):
Yes I confirm
@ccrims0n commented on GitHub (Feb 2, 2016):
@Arjoni vhost config for this would be
This config will make koel available on koel.local
EDIT: DocumentRoot should be koel root.
@phanan commented on GitHub (Feb 2, 2016):
DocumentRoot should be the Koel's installation root actually.
On Tue, Feb 2, 2016 at 10:46 AM, Vivek Kumar notifications@github.com
wrote:
@ccrims0n commented on GitHub (Feb 2, 2016):
@phanan Only public directory in Laravel should be made public since making Laravel's installation public can cause security issues if not configured properly.
@phanan commented on GitHub (Feb 2, 2016):
Configure it properly then. I think the provided .htaccess should do it.
Anyway, I was giving recommendation as the one who came up with Koel's
folder structure.
On Tue, Feb 2, 2016 at 11:13 AM, Vivek Kumar notifications@github.com
wrote:
@ccrims0n commented on GitHub (Feb 2, 2016):
@phanan Ah. Got it. For koel, the DocumentRoot needs to be installation directory.