在 Elastic Beanstalk 上运行 npm install 时出现问题

Question

情况

我有一个使用 npm、bower 和 gulp 作为前端的 Laravel (5.4) 应用程序。

我在部署时已成功配置所有内容，但 npm install 或 npm install --production（在我的情况下是相同的）命令给我错误并使部署失败。

问题

当我运行eb deploy 命令时，这是来自 AWS 的“原因”响应。

Application update failed at 2017-06-07T17:08:38Z with exit status 1 and error: container_command 01-npm-install in .ebextensions/05-frontend-install.config failed.

npm WARN lifecycle npm is using /usr/bin/node but there is no node binary in the current PATH. Use the `--scripts-prepend-node-path` option to include the path for the node binary npm was executed with.
npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated minimatch@1.0.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated node-uuid@1.4.8: Use uuid module instead
npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated graceful-fs@1.2.3: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN prefer global node-gyp@3.6.2 should be installed with -g
npm WARN prefer global marked@0.3.6 should be installed with -g

> node-sass@3.13.1 install /var/app/ondeck/node_modules/node-sass
> node scripts/install.js

npm ERR! file sh
npm ERR! path sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn sh
npm ERR! node-sass@3.13.1 install: `node scripts/install.js`
npm ERR! spawn sh ENOENT
npm ERR!
npm ERR! Failed at the node-sass@3.13.1 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2017-06-07T17_08_38_740Z-debug.log.
Incorrect application version "app-5d9c-170607_190633" (deployment 40). Expected version "app-0466-170606_110037" (deployment 31).

.ebextensions/05-frontend-install.config 文件有这个内容

container_commands:
  00-npm-upgrade:
    command: "npm install -g npm@latest"
  01-npm-install:
    command: "npm install --production"
  02-gulp-install:
    command: "sudo npm install gulp"
  03-bower-install:
    command: "sudo npm install bower"
  04-bower-deploy:
    command: "sudo bower install --allow-root"
  05-gulp-deploy:
    command: "sudo npm run prod"

Answer 1

通过 EB HOOK 实现！

我通过使用自定义弹性beantalk post-deploy platform hook 解决了我的问题（听起来不错吧？）

我的04-nodenpm.config 文件有这个内容：

container_commands:
  00-entersudoi:
    command: "sudo -i"
  01-removeoldnode:
    command: " yum remove -y nodejs npm"
  02-get-noderpm:
    command: " curl --silent --location https://rpm.nodesource.com/setup_7.x | bash -"
  03-ensurecggmake:
    command: " yum install -y gcc-c++ make"
  04-installnodenpm:
    command: " yum install -y nodejs"
  05-exitsudoi:
    command: "exit"

files:
  "/opt/elasticbeanstalk/hooks/appdeploy/post/99npminstall.sh":
    mode: "000755"
    owner: root
    group: root
    content: |
      #!/usr/bin/env bash
      cd /var/app/current/
      sudo npm install -g gulp bower laravel-elixir
      sudo bower install --allow-root
      sudo gulp --production

解决问题的部分在files: 下，我在其中手动添加带有content: 的/opt/elasticbeanstalk/hooks/appdeploy/post/99npminstall.sh 文件，作为部署后操作 使npm install ... 和所有东西我想要。

TL;DR:

npm 似乎在 container_commands 上并不完全可用。使用部署后挂钩来触发那些 npm 安装命令。

参考和有用的链接：

http://www.eq8.eu/blogs/29-aws-elasticbeanstalk-deployment-hooks https://forums.aws.amazon.com/thread.jspa?threadID=137136