將 nodejs 部署到 heroku

Question

我已經按照入門指南將 nodejs 應用程序部署到 heroku： https ://devcenter.heroku.com/articles/nodejs

它工作正常，直到git push heroku master 。 這以以下輸出結束：

git push heroku master
Counting objects: 1018, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (894/894), done.
Writing objects: 100% (1018/1018), 4.03 MiB | 64 KiB/s, done.
Total 1018 (delta 75), reused 0 (delta 0)

-----> Heroku receiving push
-----> Node.js app detected
-----> Resolving engine versions
       Using Node.js version: 0.6.20
       Using npm version: 1.0.106
-----> Fetching Node.js binaries
-----> Vendoring node into slug
-----> Installing dependencies with npm


       > ws@0.4.21 install /tmp/build_ngyi26sy7e54/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws
       > node install.js

       [ws v0.4.21] Attempting to compile blazing fast native extensions.
       [ws v0.4.21] Native code compile failed (but the module will still work):
       [ws v0.4.21] The native extensions are faster, but not required.
       [ws v0.4.21] On Windows, native extensions require Visual Studio and Python.
       [ws v0.4.21] On Unix, native extensions require Python, make and a C++ compiler.
       [ws v0.4.21] Start npm with --ws:verbose to show compilation output (if any).

       > hiredis@0.1.14 preinstall /tmp/build_ngyi26sy7e54/node_modules/socket.io/node_modules/redis/node_modules/hiredis
       > make || gmake

       cd deps/hiredis && make static
       make[1]: Entering directory `/tmp/build_ngyi26sy7e54/node_modules/socket.io/node_modules/redis/node_modules/hiredis/deps/hiredis'
       make[1]: Nothing to be done for `static'.
       make[1]: Leaving directory `/tmp/build_ngyi26sy7e54/node_modules/socket.io/node_modules/redis/node_modules/hiredis/deps/hiredis'
       node-waf configure build
       Setting srcdir to                        : /tmp/build_ngyi26sy7e54/node_modules/socket.io/node_modules/redis/node_modules/hiredis 
       Setting blddir to                        : /tmp/build_ngyi26sy7e54/node_modules/socket.io/node_modules/redis/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-Wyfk 
       'configure' finished successfully (0.029s)
       Waf: Entering directory `/home/lhk/Desktop/zwillenhomepage/node_modules/socket.io/node_modules/redis/node_modules/hiredis/build'
       Waf: Leaving directory `/home/lhk/Desktop/zwillenhomepage/node_modules/socket.io/node_modules/redis/node_modules/hiredis/build'
       Traceback (most recent call last):
         File "/tmp/node-node-Wyfk/bin/node-waf", line 16, in <module>
           Scripting.prepare(t, os.getcwd(), VERSION, wafdir)
         File "/tmp/node-node-Wyfk/bin/../lib/node/wafadmin/Scripting.py", line 145, in prepare
           prepare_impl(t, cwd, ver, wafdir)
         File "/tmp/node-node-Wyfk/bin/../lib/node/wafadmin/Scripting.py", line 135, in prepare_impl
           main()
         File "/tmp/node-node-Wyfk/bin/../lib/node/wafadmin/Scripting.py", line 188, in main
           fun(ctx)
         File "/tmp/node-node-Wyfk/bin/../lib/node/wafadmin/Scripting.py", line 386, in build
           return build_impl(bld)
         File "/tmp/node-node-Wyfk/bin/../lib/node/wafadmin/Scripting.py", line 405, in build_impl
           bld.compile()
         File "/tmp/node-node-Wyfk/bin/../lib/node/wafadmin/Build.py", line 268, in compile
           os.chdir(self.bldnode.abspath())
       OSError: [Errno 2] No such file or directory: '/home/lhk/Desktop/zwillenhomepage/node_modules/socket.io/node_modules/redis/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! 
       npm ERR! System Linux 2.6.32-343-ec2
       npm ERR! command "/tmp/node-node-Wyfk/bin/node" "/tmp/node-npm-Rq2Y/cli.js" "rebuild"
       npm ERR! cwd /tmp/build_ngyi26sy7e54
       npm ERR! node -v v0.6.20
       npm ERR! npm -v 1.0.106
       npm ERR! code ELIFECYCLE
       npm ERR! 
       npm ERR! Additional logging details can be found in:
       npm ERR!     /tmp/build_ngyi26sy7e54/npm-debug.log
       npm not ok
 !     Failed to rebuild dependencies with npm
 !     Heroku push rejected, failed to compile Node.js app

To git@heroku.com:morning-plateau-9747.git
 ! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'git@heroku.com:morning-plateau-9747.git'

我不知道如何解決這個問題。 該應用程序仍然是一個准系統。 我決定在 heroku 上啟動並運行它，然后逐步添加我想要的功能。 它在 localhost 上運行良好，npm 安裝所有依賴項都沒有錯誤，並且使用 Procfile 它甚至可以與工頭一起工作。 我已經使用 github 創建了 repo 並將其克隆到我的機器上。 部署到我的 github 帳戶沒有問題。 這是 repo 的鏈接https://github.com/lhk/zwillenhomepage

我能做什么 ？

相關 package.json：

{
  "name": "zwillen-webseite",
  "scripts": {
    "start": "server.js"
  },
  "version": "0.0.1",
  "engines": {
    "node": "0.6.x"
  },
  "dependencies": {
    "express": "3.0.x",
    "socket.io": "0.9.8",
    "jade": "0.27.0"
  }
}

Answer 1

基本上，socket.io 正在使用上下文中的hiredis 模塊。

如果您參考 eis 的回答中提到的線程，您會看到你們倆都在使用 socket.io 0.9.8。

嘗試使用 0.9.6（我在 heroku 上使用它並且從未遇到過這樣的問題）。

Answer 2

您需要通過將node_modules/hiredis添加到您的.gitignore文件來從源代碼管理中刪除它。 在heroku上的socket.io + node.js上查看完整答案

Answer 3

基本上它試圖編譯hiredis 並失敗。 這是故意的，你需要嗎？ 您的應用中是否有對hiredis 的引用？ 如果是這樣，這可能是罪魁禍首。 如果沒有，我會嘗試聯系 Heroku 支持。

另請參閱此線程。