We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
To unlock files being used by the Node.js process in the node_modules directory, there needs to be a way to shutdown the process when updating.
node_modules
Web Deploy supports this exact scenario by adding a App_Offline.htm file before sync'ing the file changes, then removing it when done.
App_Offline.htm
iisnode should check for the App_Offline.htm file and shutdown any spawed processes, and serve the App_Offline.htm file until the file is removed.
The ASP.Net Core Module does the same.
The text was updated successfully, but these errors were encountered:
This would be a good feature to add.
Sorry, something went wrong.
@ngbrown I added the app offline in the pipeline but still facing issue with one package called sharp
Related to Azure#120
No branches or pull requests
To unlock files being used by the Node.js process in the
node_modules
directory, there needs to be a way to shutdown the process when updating.Web Deploy supports this exact scenario by adding a
App_Offline.htm
file before sync'ing the file changes, then removing it when done.iisnode should check for the
App_Offline.htm
file and shutdown any spawed processes, and serve theApp_Offline.htm
file until the file is removed.The ASP.Net Core Module does the same.
The text was updated successfully, but these errors were encountered: