rauchg / slackin

Public Slack organizations made easy

Home Page:http://rauchg.com/slackin/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

azure deploy broken

guolinke opened this issue · comments

error log:

Command: bash scripts/azuredeploy.sh
Invalid start-up command "chmod +x bin/slackin && ./bin/slackin" in package.json. Please use the format "node <script relative path>".
Looking for app.js/server.js under site root.
Missing server.js/app.js files, web.config is not generated
Node.js versions available on the platform are: 0.6.20, 0.8.2, 0.8.19, 0.8.26, 0.8.27, 0.8.28, 0.10.5, 0.10.18, 0.10.21, 0.10.24, 0.10.26, 0.10.28, 0.10.29, 0.10.31, 0.10.32, 0.10.40, 0.12.0, 0.12.2, 0.12.3, 0.12.6, 4.0.0, 4.1.0, 4.1.2, 4.2.1, 4.2.2, 4.2.3, 4.2.4, 4.3.0, 4.3.2, 4.4.0, 4.4.1, 4.4.6, 4.4.7, 4.5.0, 4.6.0, 4.6.1, 4.8.4, 5.0.0, 5.1.1, 5.3.0, 5.4.0, 5.5.0, 5.6.0, 5.7.0, 5.7.1, 5.8.0, 5.9.1, 6.0.0, 6.1.0, 6.2.2, 6.3.0, 6.5.0, 6.6.0, 6.7.0, 6.9.0, 6.9.1, 6.9.2, 6.9.4, 6.9.5, 6.10.0, 6.10.3, 6.11.1, 6.11.2, 6.11.5, 7.0.0, 7.1.0, 7.2.0, 7.3.0, 7.4.0, 7.5.0, 7.6.0, 7.7.0, 7.7.4, 7.10.0, 7.10.1, 8.0.0, 8.1.4, 8.4.0, 8.5.0, 8.7.0, 8.8.0, 8.8.1, 8.9.0.
Selected node.js version 6.11.1. Use package.json file to choose a different version.
Unable to locate npm version 3.3.12
An error has occurred during web site deployment.
select node version failed
Invalid start-up command "chmod +x bin/slackin && ./bin/slackin" in package.json. Please use the format "node <script relative path>".\r\nMissing server.js/app.js files, web.config is not generated\r\nUnable to locate npm version 3.3.12\r\nD:\Program Files (x86)\SiteExtensions\Kudu\68.61122.3143\bin\Scripts\starter.cmd bash scripts/azuredeploy.sh

I just tried running the Azure deploy. Didn't see the error message that you posted, but the Azure deploy no longer works because of the CAPTCHA (#311). I see that some of the deployments (e.g. Heroku) were updated as a part of that PR, but Azure wasn't.

It would be great if it was optional (#352), but we now need to configure the environment variables: $GOOGLE_CAPTCHA_SECRET $GOOGLE_CAPTCHA_SITEKEY.

@jpoon looking at the code

eval $SELECT_NODE_VERSION
exitWithMessageOnError "select node version failed"

shouldn't exit be in some kind of smaller if? Otherwise this will always fail. That seems the reason of the mentioned problem.

The captchas environ variables are resolved in this pull: #333

I reread the error log and decided to act upon Invalid start-up command "chmod +x bin/slackin && ./bin/slackin" in package.json. Please use the format "node <script relative path>. That seems to be supported by this comment saying that sth might be wrong with script:start in package.json because the Kudo thingy reads that.

So I've changed that:
https://github.com/Code-for-All/slackin/blob/3ef754f1c8124a90ad301a3cba20b3621a6cc296/package.json#L62

But I'm still getting other errors:

Command: bash scripts/azuredeploy.sh
Using start-up script bin/slackin from package.json.
Node.js versions available on the platform are: 0.6.20, 0.8.2, 0.8.19, 0.8.26, 0.8.27, 0.8.28, 0.10.5, 0.10.18, 0.10.21, 0.10.24, 0.10.26, 0.10.28, 0.10.29, 0.10.31, 0.10.32, 0.10.40, 0.12.0, 0.12.2, 0.12.3, 0.12.6, 4.0.0, 4.1.0, 4.1.2, 4.2.1, 4.2.2, 4.2.3, 4.2.4, 4.3.0, 4.3.2, 4.4.0, 4.4.1, 4.4.6, 4.4.7, 4.5.0, 4.6.0, 4.6.1, 4.8.4, 5.0.0, 5.1.1, 5.3.0, 5.4.0, 5.5.0, 5.6.0, 5.7.0, 5.7.1, 5.8.0, 5.9.1, 6.0.0, 6.1.0, 6.2.2, 6.3.0, 6.5.0, 6.6.0, 6.7.0, 6.9.0, 6.9.1, 6.9.2, 6.9.4, 6.9.5, 6.10.0, 6.10.3, 6.11.1, 6.11.2, 6.11.5, 6.12.2, 6.12.3, 7.0.0, 7.1.0, 7.2.0, 7.3.0, 7.4.0, 7.5.0, 7.6.0, 7.7.0, 7.7.4, 7.10.0, 7.10.1, 8.0.0, 8.1.4, 8.4.0, 8.5.0, 8.7.0, 8.8.0, 8.8.1, 8.9.0, 8.9.3, 8.9.4, 8.10.0, 8.11.1, 10.0.0, 10.6.0.
Selected node.js version 6.11.1. Use package.json file to choose a different version.
Unable to locate npm version 3.3.12
An error has occurred during web site deployment.
select node version failed
Unable to locate npm version 3.3.12\r\nD:\Program Files (x86)\SiteExtensions\Kudu\79.11121.3655\bin\Scripts\starter.cmd bash scripts/azuredeploy.sh

I've managed to run it via docker container on Azure.. but that doesn't solve the problem.

Some googling around led to: