blog/running-nodejs-web-apps-on-iis-with-httpplatformhandler/

[giscus[bot]]

blog/running-nodejs-web-apps-on-iis-with-httpplatformhandler/

A post about how to create a simple Node.js web app and host it on IIS with HttpPlatformHandler

https://docs.lextudio.com/blog/running-nodejs-web-apps-on-iis-with-httpplatformhandler/

[lextm]

Slow cold start is a different topic and no custom module like this can resolve that for you. So, even if you raise a feature request that's out of scope.

[MatheusPPfitscher]

Hi, thanks for the reply. My request would be for a flag to signal IIS to start the process that the HTTPPlataformHandler redirects traffic when the ApplicationPool starts. I tried settings the ApplicationPool as AlwaysRunning instead of its default of OnDemand, but the node process(in this example) only starts when the first request hits the IIS server. By default the AppPool also kills the process when idle for more then 20m and when it recycles the website, making the slow start of a whole project a bigger problem.

…

________________________________ De: Lex Li ***@***.***> Enviado: sexta-feira, 19 de julho de 2024 15:17 Para: lextm/blog ***@***.***> Cc: Matheus Petry Pfitscher ***@***.***>; Comment ***@***.***> Assunto: Re: [lextm/blog] blog/running-nodejs-web-apps-on-iis-with-httpplatformhandler/ (Discussion #23) Slow cold start is a different topic and no custom module like this can resolve that for you. So, even if you raise a feature request that's out of scope. — Reply to this email directly, view it on GitHub<#23 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AVD6RPGUDAJ5LU2KDEJF2PDZNFJ2HAVCNFSM6AAAAABLEP6VDKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMBZHAZTENA>. You are receiving this because you commented.

[MatheusPPfitscher]

I eventually figure it out!
The application Pool needs to have these settings for it to start the node process with it:
.NET CLR Version: No managed code
Managed pipeline mode: Classic
Start Mode: AlwaysRunning
Idle-Timeout: 0

If following recommended guidelines to use application pool identities, if some library needs to write data on default node locations (%username%/appdata/roaming), it also needs:
Load User Profile: True

I now have a new issue, triggering the application pool recycle by renaming/changing the web.config file kills the node process but do not restart it. Only a full recycle from IIS manager/appcmd works as expected.