A hack for role-based config in v8 deployments

It’s a pretty common requirement that deploying instances of Sitecore will require slightly different configuration on different servers. Different roles, like content management and content deployment, will require different settings and features to work. So it’s not surprising that there are a variety of approaches to how you manage this configuration in your projects.

In the past I’ve often made use of separate config files, where you have a file for “config changes needed on all servers” and then further files for “config changes needed for CM servers”, and even down to the level of “config changes needed on server CD01” if necessary. This works fine if your deployment process understands which files should go on which servers.

Recently, however, Sitecore have started to offer a “role based configuration” approach in the configuration of v9 – so you can deploy a single config file and the server can pick and choose sections of its configuration based on what role it is performing. But back in the real world, most of us are still supporting V8 (and older) sites, so is it possible for them to adopt something similar to this idea? Here’s one approach that achieves something similar: Continue reading


If you have to use Ninject with Solr…

My first time having to configure Solr for Sitecore recently taught me a variety of new things. (I know – how have I managed to avoid it this long?) Most of the basics of the setup have been well documented elsewhere, so I won’t repeat any of that. However setting up the site to use the Ninject DI container wasn’t as smooth as the documentation suggested, so here are some notes on the issues I hit in case you find yourself stuck: Continue reading

The curious case of what happened to my Indexing Manager

I’ve spent the last week or so working on the config changes necessary to migrate a client site running Sitecore v8.1 from using Lucene to Solr for its search infrastructure. I’ve not worked much with Solr before, so this has been a good opportunity for me to learn about how it works and how it gets configured. But when I deployed my changes from my local development environment to a central testing server I discovered some odd behavior which Google didn’t help with. So, for the good of search indexes everywhere, here’s what happened… Continue reading

So you’re thinking about an upgrade?

I’ve been involved in a few discussions about the scope of projects to upgrade existing Sitecore instances in the last few weeks, and quite a lot of that discussion has focused around the “development environment” aspects of the upgrade work. So I thought I would write down some of the things that have come up in my conversations. This isn’t supposed to be a “how-to” guide, or a complete list of everything you need to worry about. But hopefully this post will provoke thought and discussions on some important topics around what might need to change – especially if you’ve not done an upgrade before… Continue reading

How to shoot yourself in the foot with a config patch…

Sitecore config patches are great, right? We (should) all be using them to ensure that our changes in configuration don’t get stomped on when we upgrade, or install new modules. But like any bit of technology, they can sometimes cause problems. Here’s an example of one I saw recently, in the hope it can save others from similar issues: Continue reading