This configuration requires that I enable distributedCall and list each of the servers in the environment in umbracoSettings.config. Right now I have this set up in a test environment, but for production I will need to have a different set of servers in the umbracoSettings.config.
Is there an Umbraco deployment tool where you can define different environments with different configuration files? Does Courier handle scenario at all?
A bit late on this reply but maybe this can help someone eventually
You can change your .csproj to run xmltransforms on all the .config files on the /Config folder and subfolders. Just add this snippet and when you publish under a certain configuration, if you have a config transform for that configuration, it will just use it.
Deploying different umbracoSettings.config for different environments
I have an Umbraco site on a load balanced environment, where the site files are stored on a centralized network share, as describe on this wiki, http://our.umbraco.org/documentation/Installation/load-balancing. ;
This configuration requires that I enable distributedCall and list each of the servers in the environment in umbracoSettings.config. Right now I have this set up in a test environment, but for production I will need to have a different set of servers in the umbracoSettings.config.
Is there an Umbraco deployment tool where you can define different environments with different configuration files? Does Courier handle scenario at all?
Thanks in advance.
In Visual studio you can apply config transforms for different environment.
To use it on the umbracosettings.config file you will need to install VS extension called SlowCheetah.
Dave
A bit late on this reply but maybe this can help someone eventually
You can change your .csproj to run xmltransforms on all the .config files on the /Config folder and subfolders. Just add this snippet and when you publish under a certain configuration, if you have a config transform for that configuration, it will just use it.
So no need for any plugin actually.
This saved my sanity. Thanks Diogo.
As an FYI I found that I needed to use:
<Target ... AfterTargets="CopyAllFilesToSingleFolderForMsdeploy">
Also to increament the client dependency framework version id checkout this topic.
is working on a reply...