Ebextension commands that run before the 04_preload_nfigĬommand: c:\windows\system32\inetsrv\appcmd.exe set config /section:applicationPools "/.processModel.idleTimeout:0.00:00:00"Ĭommand: c:\windows\system32\inetsrv\appcmd.exe set config /section:applicationPools "/.autoStart:true"Ĭommand: c:\windows\system32\inetsrv\appcmd.exe set config /section:applicationPools "/. What am I missing and how do I set preloadEnabled to true? If I terminal into the Elastic Beanstalk instance and run these commands at the command prompt, everything is setup properly. However, upon deployment, the website's preloadEnabled setting still remains at false. There are 3 other files that run before this one to setup the application pool (see below). ebextensions folder:įile: 04_preload_nfig commands:Ĭommand: c:\windows\system32\inetsrv\appcmd.exe set app "Default Web Site/" /preloadenabled:true Each time, I will need to reinstate the preload settings through the command below after installation has completed: appcmd set app '/' /preloadEnabled:true This is because the default value for preloadEnabled is 'false'.Typically this is accomplished by c:\windows\system32\inetsrv\appcmd.exe set app "Default Web Site/" /preloadenabled:true, among others. I have a vendor application that will uninstall and reinstall an application in IIS. However, I would like to set it to preload so that it goes through initialization without someone having to hit the website. NET Core app deployed to Elastic Beanstalk under Windows/IIS platform.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |