Hi,
Looks like you're pushing the node_modules folder as part of your website,
make sure to specify which npm modules you need according to heroku's
instructions but not to push the node_modules folder.
Specifically your error is due to you pushing the binary nowjs dependency
'node-proxy`, which cannot run on heroku's systems dude to different
architectures between your computer and there servers.
Eric
On Sun, Feb 5, 2012 at 4:37 AM, Zeeshan Hanif <zeeshanha...@gmail.com>wrote:
> I wanted to up my app on Heroku but while upload my app on heroku its
> give error which can be seen by 'heroku logs' command.
> Below is the error
> 2012-02-05T11:17:09+00:00 app[web.1]: message: '/app/node_modules/
> now/bin/proxy.node: invalid ELF header' }
> 2012-02-05T11:17:09+00:00 app[web.1]: Error: /app/node_modules/now/bin/
> proxy.node: invalid ELF header
> 2012-02-05T11:17:09+00:00 app[web.1]: at Module.load (module.js:
> 336:31)
> 2012-02-05T11:17:09+00:00 app[web.1]: at Function._load (module.js:
> 297:12)
> 2012-02-05T11:17:09+00:00 app[web.1]: at require (module.js:
> 348:19)
> 2012-02-05T11:17:09+00:00 app[web.1]: at Object..node (module.js:
> 416:11)
> 2012-02-05T11:17:09+00:00 app[web.1]: at Object.<anonymous> (/app/
> node_modules/now/lib/proxy.js:10:13)
> 2012-02-05T11:17:09+00:00 app[web.1]: at Module._compile
> (module.js:404:26)
> 2012-02-05T11:17:09+00:00 app[web.1]: at Module.load (module.js:
> 336:31)
> 2012-02-05T11:17:09+00:00 app[web.1]: at Object..js (module.js:
> 410:10)
> 2012-02-05T11:17:09+00:00 app[web.1]: at Function._load (module.js:
> 297:12)
> 2012-02-05T11:17:09+00:00 app[web.1]: at require (module.js:
> 348:19)
> 2012-02-05T11:17:09+00:00 app[web.1]: Listening on 52783
> It seems to me that it is the same error which occur on nowjs
> installation with npm command and nowjs team have provided alternate
> for installation.
> Kindly guide me how can i resolve this issue on heroku.
> Regards,
> Zeeshan Hanif
--
Co-Founder @ Flotype, makers of NowJS
