Databases
StackOverflow2013
Postsdbo
PONode.Js and Socket.IO application on Heroku
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PONode.Js and Socket.IO application on Heroku
    primarykey
    data
    text
    <p>I am having this error message when I try to deploy my application on Heroku. Any suggestions? I can easily deploy my app on localhost but it doesn't work on Heroku. </p> <p>My Package.JSON is:</p> <pre><code>{ "name":"tryout", "version":"0.0.1", "private":true, "scripts":{ "start":"node app" }, "dependencies":{ "express":"3.0.0rc3", "jade":"*", "passport":"&gt;= 0.1.11", "passport-local":"&gt;= 0.1.3", "underscore":"&gt;= 1.3.3", "socket.io":"&gt;= 0.9.6", "node-uuid":"&gt;= 1.3.3", "mongoose":"&gt;= 3.0.2", "bcrypt":"&gt;= 0.7.1" }, "engines": { "node": "0.8.x", "npm": "1.1.x" } } </code></pre> <p>PS: I don't use hiredis at all. </p> <p>Input command is: <code>git push heroku master</code></p> <pre><code>Counting objects: 1731, done. Delta compression using up to 8 threads. Compressing objects: 100% (1541/1541), done. Writing objects: 100% (1731/1731), 7.42 MiB | 400 KiB/s, done. Total 1731 (delta 192), reused 0 (delta 0) -----&gt; Removing .DS_Store files -----&gt; Node.js app detected -----&gt; Resolving engine versions Using Node.js version: 0.8.14 Using npm version: 1.1.65 -----&gt; Fetching Node.js binaries -----&gt; Vendoring node into slug -----&gt; Installing dependencies with npm npm WARN package.json socket-app@0.0.1 No README.md file found! npm WARN package.json jade@0.27.2 No README.md file found! &gt; hiredis@0.1.14 preinstall /tmp/build_37k5gxae7u8vc/node_modules/hiredis &gt; make || gmake cd deps/hiredis &amp;&amp; make static make[1]: Entering directory `/tmp/build_37k5gxae7u8vc/node_modules/hiredis/deps/hiredis' make[1]: Nothing to be done for `static'. make[1]: Leaving directory `/tmp/build_37k5gxae7u8vc/node_modules/hiredis/deps/hiredis' node-waf configure build Setting srcdir to : /tmp/build_37k5gxae7u8vc/node_modules/hiredis Setting blddir to : /tmp/build_37k5gxae7u8vc/node_modules/hiredis/build Checking for program g++ or c++ : /usr/bin/g++ Checking for program cpp : /usr/bin/cpp Checking for program ar : /usr/bin/ar Checking for program ranlib : /usr/bin/ranlib Checking for g++ : ok Checking for node path : not found Checking for node prefix : ok /tmp/node-node-jj2B 'configure' finished successfully (0.056s) Waf: Entering directory `/Users/USERNAME/Developer/Sites/bla/node_modules/hiredis/build' Waf: Leaving directory `/Users/USERNAME/Developer/Sites/bla/node_modules/hiredis/build' Traceback (most recent call last): File "/tmp/node-node-jj2B/bin/node-waf", line 16, in &lt;module&gt; Scripting.prepare(t, os.getcwd(), VERSION, wafdir) File "/tmp/node-node-jj2B/bin/../lib/node/wafadmin/Scripting.py", line 145, in prepare prepare_impl(t, cwd, ver, wafdir) File "/tmp/node-node-jj2B/bin/../lib/node/wafadmin/Scripting.py", line 135, in prepare_impl main() File "/tmp/node-node-jj2B/bin/../lib/node/wafadmin/Scripting.py", line 188, in main fun(ctx) File "/tmp/node-node-jj2B/bin/../lib/node/wafadmin/Scripting.py", line 386, in build return build_impl(bld) File "/tmp/node-node-jj2B/bin/../lib/node/wafadmin/Scripting.py", line 405, in build_impl bld.compile() File "/tmp/node-node-jj2B/bin/../lib/node/wafadmin/Build.py", line 268, in compile os.chdir(self.bldnode.abspath()) OSError: [Errno 2] No such file or directory: '/Users/USERNAME/Developer/Sites/bla/node_modules/hiredis/build' make: *** [all] Error 1 sh: gmake: not found npm ERR! hiredis@0.1.14 preinstall: `make || gmake` npm ERR! `sh "-c" "make || gmake"` failed with 127 npm ERR! npm ERR! Failed at the hiredis@0.1.14 preinstall script. npm ERR! This is most likely a problem with the hiredis package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! make || gmake npm ERR! You can get their info via: npm ERR! npm owner ls hiredis npm ERR! There is likely additional logging output above. npm ERR! System Linux 2.6.32-347-ec2 npm ERR! command "/tmp/node-node-jj2B/bin/node" "/tmp/node-npm-nN2P/cli.js" "install" "--production" npm ERR! cwd /tmp/build_37k5gxae7u8vc npm ERR! node -v v0.8.14 npm ERR! npm -v 1.1.65 npm ERR! code ELIFECYCLE npm ERR! npm ERR! Additional logging details can be found in: npm ERR! /tmp/build_37k5gxae7u8vc/npm-debug.log npm ERR! not ok code 0 ! Failed to install --production dependencies with npm ! Heroku push rejected, failed to compile Node.js app To git@heroku.com:arcane-sea-8207.git ! [remote rejected] master -&gt; master (pre-receive hook declined) error: failed to push some refs to 'git@heroku.com:arcane-sea-8207.git' </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USYagiz
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COWhat happens when you run `npm install` and `npm shrinkwrap` locally? You should test your app installs okay locally before publishing it to Heroku.
      singulars
      1. PONode.Js and Socket.IO application on Heroku
      1. USColonel Panic
    2. COlocally the program worked fine but I've solved this problem with using a .gitignore file, but there is a new error that I am dealing with. I hope you will find a solution :) http://stackoverflow.com/questions/14328286/heroku-node-js-errors
      singulars
      1. PONode.Js and Socket.IO application on Heroku
      1. USYagiz
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload