+1-888-365-2779
Try Now
More in this section

Forums / Set-up & Installation / Setting my Web site as the root?

Setting my Web site as the root?

5 posts, 0 answered
  1. adam
    adam avatar
    41 posts
    Registered:
    12 Jan 2009
    24 Sep 2009
    Link to this post
    Currently, I set up my site and by default it is accessible by navigating to: www.mydomain.com/sitename which is what the installer chose.

    I'd like it to instead be accessible directly at the root of the Web site like this: www.mydomain.com.

    What are the Sitefinity 3.7 settings to control this?

    Thanks!

  2. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    Registered:
    25 Nov 2016
    24 Sep 2009
    Link to this post
    Hi adam,

    Sitefinity is a Website application and it is not responsible for server configurations. You should move your website to the root of your domain. The default folder is C:\inetpub\wwwroot.

    I hope this helps.

    All the best,
    Ivan Dimitrov
    the Telerik team

    Instantly find answers to your questions on the new Telerik Support Portal.
    Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
  3. olav
    olav avatar
    76 posts
    Registered:
    22 Jan 2007
    13 Jan 2010
    Link to this post
    Hi all,

    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!

    -olav
  4. Georgi
    Georgi avatar
    3583 posts
    Registered:
    28 Oct 2016
    13 Jan 2010
    Link to this post
    Hello Olav,

    Generally there are no issues publishing Sitefinity web site to the web sites root. You are right about the configuration inheritance though. It comes from the .net framework and the way asp.net works, so it will be the same as in IIS6 - you will see the inheritance using IIS7.5. 

    You can stop the inheritance by following this article - http://www.kowitz.net/archive/2007/05/16/stopping-asp.net-web.config-inheritance.aspx

    For any collections of config properties, not caught by the location path, you can use <clear> or <remove>.

    I hope this helps.

    Regards,
    Georgi
    the Telerik team

    Instantly find answers to your questions on the new Telerik Support Portal.
    Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
  5. olav
    olav avatar
    76 posts
    Registered:
    22 Jan 2007
    13 Jan 2010
    Link to this post
    Thanks Georgi,
    You brought the inheritInChildApplications attribute is back from oblivion!
    The setting is not perfect for "disinheritance", but it will definitely help me now and then.

    I'm sharing the solution for the parser warning that inheritInChildApplications usually generate. Just edit the web.config element
    <configuration> 
    to include
    <configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0"

    (At first I thought the attribute was sliding toward unsupported.. Feels safer this way.)

    Good to hear that there are no issues with Sitefinity at the site root, as the name suggests :-)
    Again, thanks.

    -olav
Register for webinar
5 posts, 0 answered