mirror of
https://github.com/koel/koel.git
synced 2026-04-25 08:46:00 +03:00
[GH-ISSUE #444] How To Install 3.0.0 and above #314
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#314
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 @adamwbb on GitHub (Sep 11, 2016).
Original GitHub issue: https://github.com/koel/koel/issues/444
There is a issue with centos installs not giving you a up to date nodejs through yum.
This results in the 3.0.0 and above versions of koel to not install correctly.
Here is what to do:
install the prerequisites as normal.
then run the following commands as root user:
npm cache clean -fnpm install -g nn stableThen as a nonroot user run the following in the installation directory of your choice:
git clone https://github.com/phanan/koel.git .git checkout v3.3.1edit the .env file then run:
composer install && php artisan koel:inityou should have a working version of koel instead of coming into all the errors from a failed install.
@ArcheTwist commented on GitHub (Sep 11, 2016):
Yeah there are so many errors even trying to install this. @phanan really needs to write down a tutorial of how to actually install it and show us his setup so that people stop running into all these errors. If he setup a proper tutorial and helped then less requests would be sent in because of issues.
@BernardGoldberger commented on GitHub (Sep 11, 2016):
@ArcheTwist Most of these errors are not Koel related, and while we are here to help users as much as possible, we cannot make tutorials for every component Koel relies on.
Having said that, we do hope to have in the future an index of the most common issues users have run into. We do appreciate users that let us know issues that they have run into and what they did to fix or get around it.
@phanan commented on GitHub (Sep 12, 2016):
How is this even remotely related to a Koel's issue?
Like @bdgold just said, most, if not ALL, of the errors reported during installation are not related to Koel, but NodeJS, npm, gulp, permissions etc. We simply can't provide support down to this level.
I did. It's called the wiki. To make sure there's no mistake introduced with new releases, I've just tried to install a new Koel version from scratch on my own, and it just worked.
@phanan commented on GitHub (Sep 12, 2016):
These are the commands I run (which are identical to the wiki btw).
Here is my "setup" just in case – you'll notice nothing special anyway:
OSX El Capitan
Node v5.5.0
npm v3.9.3
PHP v7.0.0
MySQL v5.7.10