mirror of
https://github.com/koel/koel.git
synced 2026-04-25 08:46:00 +03:00
[GH-ISSUE #53] Exception After login #39
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#39
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 @riteshpuj2013 on GitHub (Dec 15, 2015).
Original GitHub issue: https://github.com/koel/koel/issues/53
Hi,
Please suggest me solution for the issue below:
Whoops, looks like something went wrong.
2/2 ErrorException in Application.php line 36: file_get_contents(/home/ritesh/koel/public/build/rev-manifest.json): failed to open stream: No such file or directory (View: /home/ritesh/koel/resources/views/index.blade.php)
1/2 ErrorException in Application.php line 36: file_get_contents(/home/ritesh/koel/public/build/rev-manifest.json): failed to open stream: No such file or directory
@phanan commented on GitHub (Dec 15, 2015):
Try
npm install.@r-jenish commented on GitHub (Dec 15, 2015):
npm install gives error. I also tried with root privileges
There are many other errors too.
also there isn't any log file created.
@riteshpuj2013 commented on GitHub (Dec 15, 2015):
Hi Phanan,
Thank you for quick response, really appreciate it.
As per your instruction in the wiki i have followed all the steps, but still i have receiving the same error on the web page as mentioned above:
ritesh@ritesh:
/koel$ sudo npm installpostinstall: cannot run in wd %s %s (wd=%s) koel@0.1.0 node node_modules/bower/bin/bower install && gulp --production /home/ritesh/koelnpm WARN lifecycle koel@0.1.0
npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.6
npm WARN optional Skipping failed optional dependency /laravel-elixir/gulp-watch/chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.6
npm WARN optional Skipping failed optional dependency /laravel-elixir/watchify/chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.6
ritesh@ritesh:~/koel$ sudo composer install
Loading composer repositories with package information
Installing dependencies (including require-dev) from lock file
Nothing to install or update
Generating autoload files
[Illuminate\Database\QueryException]
SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'riteshpuj2013@gmail.com' for key 'users_email_unique' (SQL: insert i
nto
users(name,email,password,is_admin,updated_at,created_at) values (ritesh, riteshpuj2013@gmail.com, y$pOflCR5r6Dx7qMuULwq5f.NtYVNcr3fMbuR7NH6zOKjpAZWB1zrd6, 1, 2015-12-15 07:53:56, 2015-12-15 07:53:56))
[PDOException]
SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'riteshpuj2013@gmail.com' for key 'users_email_unique'
ritesh@ritesh:~/koel$ sudo php artisan serve
Laravel development server started on http://localhost:8000/
[Tue Dec 15 13:24:14 2015] 127.0.0.1:38820 [200]: /favicon.ico
[Tue Dec 15 13:24:16 2015] 127.0.0.1:38825 [200]: /favicon.ico
@wzzle commented on GitHub (Dec 15, 2015):
Had the same issue. Fixed it by creating the dirs "public" and "bower_components" and making these writable for the user that I execute "npm install" with. Then I executed "npm install" again.
@phanan commented on GitHub (Dec 15, 2015):
First, you shouldn't
sudo npm installorsudo composer install.Second, looks like you have
composer install(and thereforeartisan db:seed) before. Just ignore the error.On Tue, Dec 15, 2015 at 3:55 PM, Ritesh Puj notifications@github.com
wrote:
@riteshpuj2013 commented on GitHub (Dec 15, 2015):
Shell asked me to run command using sudo.
ritesh@ritesh:~/koel$ npm install
npm WARN package.json asap@1.0.0 No repository field.
npm WARN package.json assert@1.3.0 assert is also the name of a node core module.
npm WARN package.json babel-traverse@6.3.19 No description
npm WARN package.json buffer@3.5.5 buffer is also the name of a node core module.
npm WARN package.json callsite@1.0.0 No repository field.
npm WARN package.json cli-usage@0.1.2 No repository field.
npm WARN package.json events@1.0.2 events is also the name of a node core module.
npm WARN package.json has-binary@0.1.6 No repository field.
npm WARN package.json has-binary-data@0.1.3 No repository field.
npm WARN package.json indexof@0.0.1 No repository field.
npm WARN package.json object-component@0.0.3 No repository field.
npm WARN package.json parsejson@0.0.1 No repository field.
npm WARN package.json parseqs@0.0.2 No repository field.
npm WARN package.json parseuri@0.0.2 No repository field.
npm WARN package.json punycode@1.4.0 punycode is also the name of a node core module.
npm WARN package.json querystring@0.2.0 querystring is also the name of a node core module.
npm WARN package.json string_decoder@0.10.31 string_decoder is also the name of a node core module.
npm WARN package.json url@0.10.3 url is also the name of a node core module.
npm WARN package.json util@0.10.3 util is also the name of a node core module.
child_process: customFds option is deprecated, use stdio instead.
make: Entering directory
/home/ritesh/koel/node_modules/bufferutil/build' CXX(target) Release/obj.target/bufferutil/src/bufferutil.o SOLINK_MODULE(target) Release/obj.target/bufferutil.node SOLINK_MODULE(target) Release/obj.target/bufferutil.node: Finished COPY Release/bufferutil.node make: Leaving directory/home/ritesh/koel/node_modules/bufferutil/build'npm WARN prefer global marked@0.3.5 should be installed with -g
npm WARN prefer global node-gyp@3.2.1 should be installed with -g
npm ERR! Linux 3.13.0-24-generic
npm ERR! argv "/home/ritesh/.nvm/versions/node/v0.12.0/bin/node" "/home/ritesh/.nvm/versions/node/v0.12.0/bin/npm" "install"
npm ERR! node v0.12.0
npm ERR! npm v2.5.1
npm ERR! path /home/ritesh/koel/node_modules/tfunk/node_modules/.bin/has-ansi
npm ERR! code EACCES
npm ERR! errno -13
npm ERR! Error: EACCES, unlink '/home/ritesh/koel/node_modules/tfunk/node_modules/.bin/has-ansi'
npm ERR! at Error (native)
npm ERR! { [Error: EACCES, unlink '/home/ritesh/koel/node_modules/tfunk/node_modules/.bin/has-ansi']
npm ERR! errno: -13,
npm ERR! code: 'EACCES',
npm ERR! path: '/home/ritesh/koel/node_modules/tfunk/node_modules/.bin/has-ansi' }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.
npm ERR! Please include the following file with any support request:
npm ERR! /home/ritesh/koel/npm-debug.log
@pyraxo commented on GitHub (Dec 15, 2015):
I'm experiencing the same issues. Running
npm install,composer install, with or withoutsudo, does not help. In addition, I've tried @wzzle's method but to no avail.@riteshpuj2013 commented on GitHub (Dec 15, 2015):
Hi Phanan,
There was one issue with folder permissions of /home/ritesh/.npm and /home/ritesh/.composer I fixed it for my user
Used following command: sudo chown -R ritesh.ritesh /home/ritesh/.npm /home/ritesh/.composer
Created a new clone of the repository in a folder name PUBLIC_DIR and I repeated all the steps exactly (without sudo) as mentioned as here: https://github.com/phanan/koel/wiki
Now, i have successfully installed and looking forward to stream music on my phone now :)
Thanks a lot for quick response
@phanan commented on GitHub (Dec 15, 2015):
Glad it works!
@riteshpuj2013 commented on GitHub (Dec 15, 2015):
Hi Phanan,
How can i run the server on different port ? For example port 80
@phanan commented on GitHub (Dec 15, 2015):
You would deploy like any other PHP website.