I’m travelling a lot more these days so spending time in hotels is now for winding down and sleeping to minimise the effects of jet lag. Something I find doesn’t actually get any easier the more you travel. I now take my Chromecast with me. It’s just one of those things that just works. No fuss or hassle. So I don’t need to spend time trying to troubleshoot problems.
In the good old days you hosted your website yourself or using a dedicated web hosting provider. Whichever option you chose you needed a machine, virtual or physical, with a full operating system that needed patching, some sort of remote access, web hosting software such as Apache or IIS and some sort of SSH or RDP access. And perhaps it’s own firewall rules. That is a lot of investment for just a blog.
Deciding on a cross-platform virtualisation technology for the Chocolatey team has always been important. But as a team who all use Apple Mac’s it became particularly important when I started sharing virtual environments with them. I use Windows 10. They all use OSX. So we decided to use VirtualBox which had the added advantage of having good Vagrant support, which was used extensively internally.
Running Docker with VirtualBox requires a bit of fiddling. Fortunately Stefan Scherer has put together an awesome solution to do just that but VirtualBox is just flaky at times. Add into the mix the unpredictable nature of Vagrant and running this mix-up of technologies can be a frustrating experience!
The Chocolatey Community Repository currently has 6,655 unique packages. When we add up the versions of each of those packages it grows to 65,549. That’s a lot of packages. A lot of storage needed to house them all. And a lot bandwidth needed for you to download them.
But the Chocolatey Community Repository is not for everybody. Chocolatey doesn’t recommend organizations use the community repository directly for several reasons.
I’ve had an disagreement recently with a colleague about the usage of open-source automation tools, especially Chocolatey in Business environments. A key point of this argument was the integration of new open source tools into long-existing, mostly commercial software based workflows.
One of the main reasons to use Chocolatey in an organization is its ability to integrate seamlessly with already existing automation infrastructure.
Getting PowerShell Core to run on Linux was easy enough. As I’m running Kubuntu 18.10 it’s a simple case of using
However, I didn’t expect running PowerShell Core on Linux to be problem free. And it wasn’t. After installing my own PsTodoTxt module from the PowerShell Gallery, PowerShell couldn’t find it.