Azure-docs: Deploy fails with other Rail projects

[mkokabi]

Hi,
When I try the sample in this page it works but if I try with a basic sample created by rails cli:

rails new demo

while I push my changes the deployment starts but it would fail with this error:

Command: "/home/site/deployments/tools/deploy.sh"
ENOENT: no such file or directory, open '/opt/nodejs/12.13.0/npm.txt'
Handling node.js deployment.
Kudu sync from: '/home/site/repository' to: '/home/site/wwwroot'
Copying file: 't1.txt'
Ignoring: .git
Detecting node version spec...
Using default version: 12.13.0
Node.js versions available on the platform are: 4.4.7, 4.5.0, 4.8.0, 6.2.2, 6.6.0, 6.9.3, 6.10.3, 6.11.0, 6.17.1, 8.0.0, 8.1.4, 8.2.1, 8.8.1, 8.9.4, 8.11.2, 8.12.0, 8.15.1, 8.16.2, 9.4.0, 10.1.0, 10.10.0, 10.14.2, 10.17.0, 12.13.0.
Resolved to version 12.13.0
Detecting npm version spec...
An error has occurred during web site deployment.
select node version failed
ENOENT: no such file or directory, open '/opt/nodejs/12.13.0/npm.txt'\n/opt/Kudu/KuduConsole/Scripts/starter.sh "/home/site/deployments/tools/deploy.sh"

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 872e5aa0-cda4-295d-08f8-4db6e488e32f
• Version Independent ID: 2b6b32d6-e501-6cb4-bb3b-c3c46851d24e
• Content: Quickstart: Create a Linux Ruby app - Azure App Service
• Content Source: articles/app-service/containers/quickstart-ruby.md
• Service: app-service
• GitHub Login: @cephalin
• Microsoft Alias: cephalin

[BryanTrach-MSFT]

@mkokabi Thanks for the feedback! We are currently investigating and will update you shortly.

[patonoide]

I'm having the same problem but with a custom rails app.

[DashleenBhandari-MSFT]

@mkokabi , Apologies for delay in response.
This is a known issue. While deploying Rails azure sometimes thinks it is a nodejs app and it starts using deployment process..
Can you try removing the package.json and test?
Please let me know if this works for you.

[DashleenBhandari-MSFT]

@mkokabi , I have not heard back from you in a couple of days. I ll go ahead and close the issue for now. Feel free to reopen in case you need further help.

[mootpointer]

I've just come upon this issue too – removing the package.json does not resolve the issue (and would cause other problems with the deployment down the line)

[shaunakv1]

This is still an issue, as its closed here, I started a new thread.