mirror of
https://github.com/koel/koel.git
synced 2026-04-26 09:15:59 +03:00
[GH-ISSUE #661] Video tapes, lies and errors #473
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#473
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 @gerroon on GitHub (Oct 10, 2017).
Original GitHub issue: https://github.com/koel/koel/issues/661
Sorry for the catchy title.
I have been trying to install Koel on my Debian testing system for half a day. I cant go morw with this. I think there is a bug somewhere because I finally thought that I did it now I am hitting these errors
I followed the tutorial on https://gist.github.com/bplower/613a99156d603abac083
https://paste.debian.net/hidden/6118977c/
thanks
@gerroon commented on GitHub (Oct 10, 2017):
Plus this
Bear in mind the node was installed as described in the tut
@gerroon commented on GitHub (Oct 10, 2017):
https://paste.debian.net/hidden/05c14ecb/
@gerroon commented on GitHub (Oct 10, 2017):
more lies
see the missing install folder
php artisan koel:init
Attempting to install or upgrade Koel.
Remember, you can always install/upgrade manually following the guide here:
📙 https://koel.phanan.net/docs
App key exists -- skipping
JWT secret exists -- skipping
Migrating database
Data seeded -- skipping
Compiling front-end stuff
ERROR: [Errno 21] Is a directory: 'install'
🎆 Success! You can now run Koel from localhost with
php artisan serve.Again, for more configuration guidance, refer to
📙 https://koel.phanan.net/docs
Thanks for using Koel. You rock!
@phanan commented on GitHub (Oct 10, 2017):
Looks like there's a problem with your
yarninstallation. Tryyarn run install?@gerroon commented on GitHub (Oct 10, 2017):
yarn run install ⏎
ERROR: [Errno 2] No such file or directory: 'run
@phanan commented on GitHub (Oct 10, 2017):
Then clearly it's your
yarninstallation.@gerroon commented on GitHub (Oct 10, 2017):
npm ERR! koel@ postinstall: yarn build │······················
npm ERR! Exit status 1 │······················
npm ERR! │······················
npm ERR! Failed at the koel@ postinstall script. │······················
npm ERR! This is most likely a problem with the koel package, │······················
npm ERR! not with npm itself. │······················
npm ERR! Tell the author that this fails on your system: │······················
npm ERR! yarn build │······················
@kevinboulain commented on GitHub (Oct 10, 2017):
Here are my installation notes on a Debian Stretch LXC (so the script should list all or most of the needed packages):
I got stuck on some problems from yarn but got the missing piece here: #656.
Adapt it to your needs but this should be enough to get you started.
@gerroon commented on GitHub (Oct 10, 2017):
@ether42
Thanks for your reply, I appreciate that instead of blaming me or my system you offered a solution that too 3 mins to install and apply.
It works except that I cant login. I tried changing changing the admin stuff in .env it did not work.
Did you have an issue with login? Do I need to do something after changing admin stuff in the env file?
@gerroon commented on GitHub (Oct 10, 2017):
I also hope that the dev prepares a less sloppy and up to date documentation, it seems like everyone wasted 2 days on this which is alot of man hours
@phanan commented on GitHub (Oct 10, 2017):
Well it's your system so I'd say you're in the best position to make it work.
Yarndoesn't work like it should is hardly Koel's or its developer's fault. In fact, normally I would just close these yarn/npm related "issues."The linked tutorial is non-official. Koel doesn't and will never provide a documentation on how to install Node.js, npm, or yarn, for the same reasons it won't for PHP/MySQL/Apache.
I'm glad that you're having your problems sorted, but it would be appreciated if you could remind yourself that open source developers don't owe you anything. Your "2 days wasted which is a lot of man hours" is nothing compared to our countless hours spent to design, develop, and fix these applications for you to use – totally free of charge.
@gerroon commented on GitHub (Oct 10, 2017):
It was not my system your documentation did not provide the correct yarn therefor I wasted close to 2 days on it (vs 5 mins total install time with correct yarn version), and if you look at your bugs and replies to gists you will see alot of people have installation issues. You can try to make the pain ease a bit
Not everyone is a js developer.
@gerroon commented on GitHub (Oct 10, 2017):
Also I am sorry that I am a dumb duck and I cant install and use your free application. If you want people to use this so called free app, please make the installation easier. Maybe provide a distribution that has all the necessary components.
Sure my wasted 2 days is nothig compared to your many hours, but if 100 people wasted 2 days on this app now you have 200 wasted man days. Not enough to bring to attention?
Anyway I do not want to dwell on this and waste more of my time and your time. Thanks for developing the app.