One can set the preloadEnabled on both a Site and Application-level in IIS, however the current Ansible module for IIS only appears to have this option on the Site-level.
At work, we currently have a handful of applications under the same website so that they are on the same domain, e.g. site.com/app1, site.com/app2, etc. We have these applications configured under their own application pools such that one API / site error will not take down the pool for another.
In this specific case, we have a need for an application pool running with startMode: alwaysRunning and the application running with preloadEnabled: true.
SUMMARY
One can set the
preloadEnabled
on both a Site and Application-level in IIS, however the current Ansible module for IIS only appears to have this option on the Site-level.See Also: https://github.com/ansible/ansible/issues/66831
ISSUE TYPE
COMPONENT NAME
community.windows.win_iis_webapplication
ADDITIONAL INFORMATION
At work, we currently have a handful of applications under the same website so that they are on the same domain, e.g.
site.com/app1
,site.com/app2
, etc. We have these applications configured under their own application pools such that one API / site error will not take down the pool for another.In this specific case, we have a need for an application pool running with
startMode: alwaysRunning
and the application running withpreloadEnabled: true
.See: https://docs.hangfire.io/en/latest/deployment-to-production/making-aspnet-app-always-running.html