[GH-ISSUE #215] Can this run on apache? #154

Closed
opened 2026-02-26 02:32:18 +03:00 by kerem · 7 comments
Owner

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?

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?
kerem closed this issue 2026-02-26 02:32:18 +03:00
Author
Owner

@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

<!-- gh-comment-id:178129595 --> @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
Author
Owner

@zazatek commented on GitHub (Feb 1, 2016):

Yes I confirm

<!-- gh-comment-id:178191974 --> @zazatek commented on GitHub (Feb 1, 2016): Yes I confirm
Author
Owner

@ccrims0n commented on GitHub (Feb 2, 2016):

@Arjoni vhost config for this would be

<VirtualHost *:80>
  ServerName koel.local
  DocumentRoot <Absolute path to koel>
  ErrorLog <Absolute path to error log for this vhost>
</VirtualHost>

This config will make koel available on koel.local

EDIT: DocumentRoot should be koel root.

<!-- gh-comment-id:178327416 --> @ccrims0n commented on GitHub (Feb 2, 2016): @Arjoni vhost config for this would be ``` <VirtualHost *:80> ServerName koel.local DocumentRoot <Absolute path to koel> ErrorLog <Absolute path to error log for this vhost> </VirtualHost> ``` This config will make koel available on koel.local EDIT: DocumentRoot should be koel root.
Author
Owner

@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:

@Arjoni https://github.com/Arjoni vhost config for this would be

<VirtualHost *:80>
ServerName koel.local
DocumentRoot
ErrorLog

This config will make koel available on koel.local


Reply to this email directly or view it on GitHub
https://github.com/phanan/koel/issues/215#issuecomment-178327416.

<!-- gh-comment-id:178332176 --> @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: > @Arjoni https://github.com/Arjoni vhost config for this would be > > <VirtualHost *:80> > ServerName koel.local > DocumentRoot <Absolute path to public folder in koel> > ErrorLog <Absolute path to error log for this vhost> > </VirtualHost> > > This config will make koel available on koel.local > > — > Reply to this email directly or view it on GitHub > https://github.com/phanan/koel/issues/215#issuecomment-178327416.
Author
Owner

@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.

<!-- gh-comment-id:178337937 --> @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.
Author
Owner

@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:

@phanan https://github.com/phanan Only public directory in Laravel
should be made public since making Laravel's installation public can cause
security issues if not configured properly.


Reply to this email directly or view it on GitHub
https://github.com/phanan/koel/issues/215#issuecomment-178337937.

<!-- gh-comment-id:178347550 --> @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: > @phanan https://github.com/phanan Only public directory in Laravel > should be made public since making Laravel's installation public can cause > security issues if not configured properly. > > — > Reply to this email directly or view it on GitHub > https://github.com/phanan/koel/issues/215#issuecomment-178337937.
Author
Owner

@ccrims0n commented on GitHub (Feb 2, 2016):

@phanan Ah. Got it. For koel, the DocumentRoot needs to be installation directory.

<!-- gh-comment-id:178354022 --> @ccrims0n commented on GitHub (Feb 2, 2016): @phanan Ah. Got it. For koel, the DocumentRoot needs to be installation directory.
Sign in to join this conversation.
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#154
No description provided.