mirror of
https://github.com/koel/koel.git
synced 2026-04-25 08:46:00 +03:00
[GH-ISSUE #126] Gulp Issue #88
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#88
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 @caleuanhopkins on GitHub (Dec 20, 2015).
Original GitHub issue: https://github.com/koel/koel/issues/126
Trying to run
gulp --productionafter runningnpm installandbower installbut it looks like my gulp task is not working properly as my public directory is not being created.I have to run gulp with
sudodue to permission issues on my raspberry pi running raspbian and other software I have running on the pi. Shouldn't make a difference in my opinion though, but correct me if I'm wrong on this.@phanan commented on GitHub (Dec 21, 2015):
Don't think this is a Koel issue per-se.
@caleuanhopkins commented on GitHub (Dec 21, 2015):
@phanan can you please explain why this isn't 'Koel Issue per-se'? I'm try to run the build script as outlined in the installation documentation and yet it's not resulting as it should according to the documentation. There is no output showing any errors that I can use to debug the issue, therefore it IS a Koel issue.
@phanan commented on GitHub (Dec 21, 2015):
I don't recall documenting a
sudoanywhere. If your environment is set up in a way that you need to rely onsudo, I'd say something is definitely wrong from the start.Koel is built on top of a lot of other packages and libraries, two of which are Gulp and Laravel's Elixir, which in turn rely on Node/npm. If your installation of Node/npm is not working with Gulp/Elixir for whatever reason, I'd suggest you to explore and fix from there, not from Koel itself. As a matter of fact, I wouldn't be able to support you on this even if I had enough time, simply because I'm not a Gulp/Elixir/Node expert.
@caleuanhopkins commented on GitHub (Dec 21, 2015):
@phanan thanks for the expanded reply. Yes there is no sudo in the documentation, it's due to the fact I'm running the software on raspberry pi Linux software. I'll will look further into this issue myself