22 Jan 2007
13 Jan 2010
Link to this post
We're about to go live with our company site, using Sitefinity standard, and I'd like to hear opinions about publishing the app to the site root, considering Sitefinity specific issues or other.
At the same time we are publishing two additional apps (one of them Sitefinity) to the same IIS7.5 server, and we will offer or require SSL for all.
If we proceed using subdomains (app1.oursite.com, app2.oursite.com) and separate web sites for each additional app, we are currently running out of unused subdomains covered by our certificate (EV SAN SSL cert at the Forefront edge server), and would have to order an extended certificate. And the trouble would haunt us with the third app that we don't know the best name for yet, and so on.
On the other hand, if we proceed using subfolders (oursite.com/app1, oursite.com/app2) and the same web site for each app, we will not have any issues with certificates.
But I seem to remember, one time using IIS6, running into unintentional inheritance of application settings from oursite.com to oursite.com/appX.
Can this be easily avoided now? (think I stumbled upon something, just can't remember..)
If not, I guess I'll have to put our company site in an subfolder and redirect the site root folder.
Would greatly appreciate ideas and comments!