Usergroup: Developing Sitecore code under Docker

I presented a session at the London and Manchester user groups recently, where I talked about what I needed to do in order to get started developing Sitecore code under Docker.

Making an “XP without analytics” Docker image for Sitecore

One of the minor annoyances of some XM releases of Sitecore is that rather than just disabling analytics and not running xConnect, they do not include the DLLs necessary for personalisation at all. That can be a bit of a pain sometimes – as I discovered recently when I tried to deploy some client code into an XM docker container. The site broke because the client code included references to a personalisation DLL – which made me realise I actually wanted an “XP in XM mode” container so I didn’t need to bother with the memory and CPU for xConnect. So here’s how I hacked one up…

Attaching a debugger to Sitecore in Docker

The approach I read on how to “how to attach your debugger to Sitecore inside Docker” by running “docker inspect” to fetch the current IP address, and pasting it into Visual Studio can be a bit of a faff. So I got to wondering: Are there other ways to achieve the same result?

Docker and LinkManager playing nicely…

Having started down the Docker road, I hit an interesting issue the other day. How do you get Sitecore to generate absolute links correctly when your site runs inside a container?

Building Docker images for older versions of Sitecore

There’s been a lot of movement towards “Docker for Sitecore” over the last year – to the extent that even I have finally jumped onto the bandwagon. And with any new tech, there are some rough edges to contend with. Right now (for me at least) one of those is being able to get the right Docker images built for the bit of work you need to do. In the future (crosses fingers) we’ll see Sitecore offering a repo for these images – but for now it’s up to us to build our own. So if you need something that’s not v9.3, here’s what I did to get there: