Using the redis Docker container locally

To develop applications with the redis database we can use a Docker image.

The documentation is at

Set up the redis container to be accessed via localhost on the local computer

Start the redis container

Start the redis container “detached” ( -d ) in the background and expose it through localhost:6379

  • In the terminal execute
    docker run -dit --name redis -p redis

Check if the container running

  • In the terminal execute
    docker ps -a

Test the redis database

Start a shell session in the redis container to access the command line utility

  • In the terminal execute
    docker exec -it redis sh
  • At the # prompt start the redis cli
  • At the> prompt test the connection
    The response should be “PONG”
  • Store a value
    set cat 10
    The response should be “OK”
  • Retrieve the value
    get cat
    The response should be “10”
  • Get the list of all keys
    keys *

Set up redis to be used by other Docker containers

Create a network

Create a Docker network, so multiple containers can communicate with each other using it.

  • In the terminal execute
    docker network create redis

Start the redis container

Start the redis container “detached” ( -d ) in the background in the “redis” network to make it available for redis-cli.

  • In the terminal execute
    docker run --name redis --network redis -d redis

Start the redis command line utility

  • In the terminal execute
    docker run --name redis-cli -it --network redis --rm redis redis-cli -h redis

Using the redis command line utiliy

Store a value in the redis database
  • In the terminal execute
    set cat 10
Read a value from the redis database
  • In the terminal execute
    get cat

DeprecationWarning: Access to process.binding(‘http_parser’) is deprecated.

When you try to run an older Node.js application under a new version of Node.js you may get deprecation warnings. If you downgrade Node.js and keep the out of date component, you will introduce a dangerous security risk in your application.

To refresh the referenced Node.js libraries

  • In the command line execute
    npm install --force
    npm audit fix --force

DevOps Engineering part 1. (Win) – Make your Windows computer easier to use

Set up your computer

Display the file extensions

On Windows 11

  • Open the File Explorer
  • Click the arrow next to View and select Show
  • Mark File name extensions and Hidden items

On Windows 10

  • Open File Explorer
  • On the View tab select
    • File name extensions
    • Hidden items

On Windows 7

(if you accidentally run into an ancient machine)

  • Open Windows Explorer and select Organize
  • Select Folder and search options
  • On the View tab
    • Select Show hidden files, folders, and drives
    • Uncheck Hide extensions for known file types

Disable the Windows key

If you use a Macintosh computer, you use the Command key all the time. Unfortunately, on the Windows keyboard you will always accidentally hit the Windows key. This can be very frustrating, as pressing the Windows key with any of the cursor keys will resize the current window.

To disable the Windows key

  • Download the 64 bit version of PowerToys by Microsoft (currently PowerToysSetup-0.68.1-x64.exe) from
  • Execute the installer file to install the application
  • Start Powertoys
  • On the left side select the Keyboard manager
  • Click the Open Settings button
  • Select Remap a key
  • Click the plus sign
  • On the left side select Win (Left), on the right side select Disable and click the OK button.
  • Click Continue Anyway

Nice to have utilities



WinDirStat is a disk utility to display the relative size of your files in a graphical interface and provide a tree view to help to find them.

Download it from

Install the DevOps development tools on Windows


If you want to host Chocolatey packages internally install Chocolatey. See Install Chocolatey

Store your username in an environment variable

We will use it in the .kitchen.yml file of the Chef SDK.

  1. Open the Git Bash window and execute the command echo ‘export USER=`whoami | tr -d “\\n”`’ >> ~/.bashrc

Virtual Box

Download Virtual Box from and follow the instructions to install it.

At the time of writing, this was the section where the installer files were referenced


Run the downloaded installer file and accept all default values.

The installer starts the Virtual Box application.You can close it, we will use other tools to start it in the future.

To be able to launch 64 bit guest operating systems turn off Hyper-V in Windows Features

  1. In the Windows search box enter Windows Features and select Turn Windows Features on or off,
  2. Uncheck Hyper-V and click OK,
  3. Reboot the computer for the setting to take effect.

Configure VirtualBox


To share the connectivity of the host computer with the virtual machine, mainly if you use VPN

  1. In Virtual box click Settings
  2. Select Network
  3. Attach the network adapter to NAT

Copy and paste

To enable copy and paste between the virtual machine and the host ( your workstation )

  1. On the General tab of the Settings page select the Bidirectional shared clipboard

Shared Folders

Specify the shared folder on your workstation

  1. In the VirtualBox menu select Preferences
  2. On the Shared Folders tab click the + icon
  3. To share the entire system drive, select the C: drive of your workstation

Enable shared folders on the virtual machines

To enable the shared folders on the virtual machine and other configurations see Virtual machine configuration at VirtualBox


For Vagrant installation see Vagrant.


  • Download Ruby from
  • Install the 32 bit version, as the 64 bit version is fairly new and has compatibility issues. Download the latest Ruby installer. Pick the file that does not have the (x64) at the end.
  • Accept the default values but check Add Ruby executables to your PATH

 Ruby Development Kit

The Ruby Development Kit is need for certain Ruby gems, so install it.

  • Download the Ruby Development Kit from the DEVELOPMENT KIT section of
  • If you have installed the 32 bit version of Ruby make sure you install the 32 bit version of the DevKit. Select the Development kit that matches the Ruby version you installed. At the time of writing the latest development kit is under “For use with Ruby 2.0 and above (32bits version only)
    • Run the installer to extract it to a permanent location (C:\RubyDevKit)
    • Open a command window in the C:\RubyDevKit folder
    • Run these commands in the command prompt to install it.
      • ruby dk.rb init
      • ruby dk.rb install
  • For more information see

Chef Development Kit

Terraform by Hashicorp

Install it with Chocolatey

  • Open a Git Bash window as administrator
  • Execute choco install terraform


Manual installation

  • Download Terraform from
  • Unzip the downloaded package to C:\HashiCorp\Terraform
  • Add the Terraform directory to the path of the computer. It is not added automatically on 64 bit Windows.
    • In Windows Explorer right-click Computer and select Properties,
    • On the left side select Advanced System Settings,
    • At the bottom click the Environment Variables… button,
    • In the System Variables box select Path and click the Edit… button,
    • Add the following to the end of the Variable value. (Don’t forget to start with the semicolon as the separator). ;C:\HashiCorp\Terraform
  • To create RDS (Relational Database Service) instances in AWS, install the Amazon Web Services Command Line Interface (See instructions below)
  • Configure the GitBash window to run as administrator to be able to execute the “terraform get” command to get local modules during development
    • Right click the shortcut of the Bash window you use and select Properties
    • On the Compatibility tab check Run this program as an administrator

For more details see


Graphviz is a Dependency Graph Visualization Software. We will use this utility to display the Terraform graphs.

  • Download from
    There are really two dots in the address :-)
  • Execute the installer
  • You may need to add the location to the Path environment variable. Make sure you use the actual folder name, as it contains the version of the application. ;C:\Program Files (x86)\GraphvizX.XX\bin


The Amazon Web Services command line interface installation will set up your workstation to launch instances in AWS from Test Kitchen. If you know you will work with AWS, see DevOps Engineering part 3. – Working with AWS for the AWS CLI installation.


We use Packer to create custom AWS AMIs that contain the fundamental configuration and applications that are common in every instance we launch.

Install with Chocolatey

  • Open a Git Bash window as administrator
  • Execute choco install packer


Manual Installation

Install software development tools on Windows

Text Editor

Notepad ++

Install a good text editor. If you do not have a favorite, I recommend Notepad ++

Configure Notepad ++

Tab settings

  • In the Settings menu select Preferences
  • In the Language section set the Tab size to 2 and select Replace by space

Visual Studio Code

Configure Visual Studio Code


For Git installation and configuration see Install Git on Windows


To automatically pretty print JSON responses in Chrome


To install Make to be able to run it in the Git Bash (MINGW64) window

  1. Navigate the ezwinports at
  2. Download the or newer archive (make sure you select the version “without-guile”),
  3. Extract the zip archive in a temporary location,
  4. Copy the contents to the C:\Program Files\Git\mingw64 directory, merging into the existing folders, but do NOT overwrite or replace any existing files.


To be able to work with Amazon Web Services install the AWS CLI

Configure the AWS CLI

This process with create the ~/.aws/credentials and ~/.aws/config files

  • In the terminal execute
    aws configure
  • Enter the aws key, aws secret key, and specify the default region and response format (usually json is used)

xcrun: error: invalid active developer path on macOS


After a major macOS upgrade (currently to Ventura) the command line tools, including git, in the terminal windows (Terminal, iTerm) stop working. We get the error message

xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools), missing xcrun at: /Library/Developer/CommandLineTools/usr/bin/xcrun


The macOS terminals use the Xcode Command Line Tools to execute commands on the Mac. When you upgrade the Macintosh operating system, you need to accept the licensing agreement of the Xcode Command Line Tools.


The simplest way to do it, to re-install the Xcode Command Line Tools and click the Accept button.

  • Open a terminal window and execute
    xcode-select --install
  • The installation starts, and when prompted, Accept the license terms and complete the installation.


  • If after the re-installation you still get the same error message, try to execute
    sudo xcode-select --reset

There is a double quote at the end of the value read from the .env file

Developers frequently use the .env file to store configuration values on the workstation. If the values contain sensitive data add the line to the .gitignore file to avoid committing the file into source control.


If the value contains spaces, enclose it in double quotes



Your application reads a double quote at the end of the value:
gDebugColumnName: x Debug”


There is an extra space character at the end of the line after the closing double quote in the .env file


Delete all trailing spaces from the lines in the .env file.

KSP2 Modding with SpaceWarp

Install SpaceWarp

To install SpaceWarp you need the following tools installed on your computer

Get SpaceWarp from GitHub

  • Create a new directory external_dlls for SpaceWarp in the Kerbal Space Program 2 “C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program 2\KSP2_x64_Data\Managed” directory
    cd "C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program 2\KSP2_x64_Data\Managed
    md external_dlls
  • Clone the SpaceWarp repository in to the external_dlls directory
    cd external_dlls
    git clone

Install the Python dependencies

Build SpaceWarp

  • Open the ksp2_mod_loader_patcher.sln Visual Studio solution from “C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program 2\KSP2_x64_Data\Managed\external_dlls\SpaceWarp\SpaceWarp”
  • Open the list of references to see the missing packages

  • The packages marked with an exclamation point are missing

  • Open the NuGet package manager

Add references to the missing assemblies

  • Right-click References and select Add Reference…
  • On the Browse tab click the Browse button
  • Browse to the C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program 2\KSP2_x64_Data\Managed folder and select the DLLs
    • Assembly-CSharp.dll
    • Newtonsoft.Json.UnityConverters.dll
    • Unity.TextMeshPro.dll
    • UnityEngine.dll
    • UnityEngine.AssetBundleModule.dll
    • UnityEngine.CoreModule.dll
    • UnityEngine.IMGUIModule.dll
    • UnityEngine.InputLegacyModule.dll
    • UnityEngine.UI.dll

Rebuild the solution

  • Right-click the solution and select Rebuild Solution

Using SpaceWarp

You can also download SpaceWarp from

  • Unzip the downloaded file
  • Copy the contents (the SpaceWarp directory) into the KSP2 main directory

Maybe needed to configure Visual Studio to work with Unity

See for details

To select the installed Visual Studio version

  • Open the Unity Editor
  • In the Edit menu select Preferences
  • On the External Tools tab click the Open by file extension and select your Visual Studio version