You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This page contains some contradictions that are confusing.
In the first paragraph it states that the App Service runs npm install --production when you deploy from a Git repository or a zip file with build automation enabled. However in the Customize Build Automation section it states, in step 2, that it runs npm install without any flags. In node.js-land that is a big difference.
Also, back in the first paragraph it talks about deploying from 'a Git repository or a zip file with build automation enabled'. I think the use of 'with' there could be interpreted to mean that the build automation flag only applies when using zip file.
Also, 'deploying from a Git repository' could be interpreted as using Github Actions where npm install usually happens on a Github runner and not on Azure at all.
I write this only because I honestly found the descriptions in the article confusing; there is so little documentation on deploying node to Azure in production that if the few articles on it could be more clear it could save people hours of time.
Thanks.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
ID: 896b5d4c-ac3b-f0a2-5102-9e59bbe2ed48
Version Independent ID: 32fd9660-0d08-205c-c7f3-57b00f35e667
Thanks for the feedback @bluefirepatrick. I do want to point out a couple of things that you mentioned. The sentence you referenced, _a Git repository or a zip file with build automation enabled_.
This page contains some contradictions that are confusing.
In the first paragraph it states that the App Service runs npm install --production when you deploy from a Git repository or a zip file with build automation enabled. However in the Customize Build Automation section it states, in step 2, that it runs npm install without any flags. In node.js-land that is a big difference.
Also, back in the first paragraph it talks about deploying from 'a Git repository or a zip file with build automation enabled'. I think the use of 'with' there could be interpreted to mean that the build automation flag only applies when using zip file.
Also, 'deploying from a Git repository' could be interpreted as using Github Actions where npm install usually happens on a Github runner and not on Azure at all.
I write this only because I honestly found the descriptions in the article confusing; there is so little documentation on deploying node to Azure in production that if the few articles on it could be more clear it could save people hours of time.
Thanks.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: