site.config

I have added a small feature for configuring sites outside the web.config - let's see if Ole approves it.

In the site resolver, I have added functionality to look for a site.config file in the current directory. If such a file exists, the site configuration is read from that file. This make it possible to define sites much more flexible (at a cost of course).

Here is an example of a site.config file:
<site
rootPath="/sitecore/content"
startItem="/home"
language="en"
database="core"
domain="sitecore"
loginPage="/sitecore/login"
content="master"
enableWorkflow="true"
xmlControlPage="/sitecore/shell/default.aspx"/>

You can also use a reference to a site defined in the web.config. In that case the site.config file looks like this:

<site reference="shell">

The cost of this is performance. For each request, Sitecore has to check for the existance of a site.config file. If found, the file is read and parsed into an Xml document. While not overly concerning, it does hurt performance slightly.

What it doesn't do: A site.config file does not work recursively on folders. Sitecore does not look for site.config files in parent folders, so you will have to place a site.config in every subfolder. The reason for this is performance.