Brian J. Bayer brianjbayer

Kubernetes in Docker Desktop for Mac

What this is (the simplest thing that might possibly work)

Probably the simplest way you can get started with Kubernetes (k8s) on a Mac (or run a local development environment) is with the single-node Kubernetes cluster built into Docker Desktop.

Use RSpec Rails System Specs for Web Server Level Functional Tests

🕐 Updated March 2024

Why

Test all of your Rails app's functionality even at the highest feature level right in RSpec with the rest of your unit and integration tests.

Adding WebDriverManager.Net to your C#-Selenium Project

What This Is

This is the basic gist (and why) of adding the WebDriverManager.Net Package to your C#-Selenium web browser automation project.

Add a docker-compose Framework to Your Browser Tests (Part 1 of 3)

Simplify running and testing your tests and maybe even get more people to run and use them.

Add a simple but easy-to-use docker-compose orchestration framework using a Selenium Standalone browser container

Add a docker-compose Framework to Your Browser Tests (Part 2 of 3)

Simplify running and testing your tests and maybe even get more people to run and use them.

Add a simple but easy-to-use docker-compose orchestration framework using a Selenium Standalone browser container

Add a docker-compose Framework to Your Browser Tests (Part 3 of 3)

Simplify running and testing your tests and maybe even get more people to run and use them.

Add a simple but easy-to-use docker-compose orchestration framework using a Selenium Standalone browser container

Using PhantomJS in Capybara RSpec

Before there was headless Chrome and Firefox, there was the PhantomJS headless browser.

With the rise of headless Chrome and Firefox and lack of active contributors, PhantomJS development has been

Docker Environment Variables Cheat Sheet

There are two sets of separate and independent environment variables to consider in Docker...

Local environment variables in the shell where you are calling the docker/docker-compose commands, like your laptop, CI/CD, or production server)
Container environment variables in your running containers

There are two basic concepts when using environment variables in Docker...

	#!/bin/sh
	# This script builds the image with either the specified argument
	# or default git long sha of the last commit

	IMAGE_NAME=${IMAGE_NAME:-SET-THE-dockerid/repository-name}

	must_be_git_repos() {
	git rev-parse --git-dir > /dev/null 2>&1
	errcode=$?
	if [ $errcode -ne 0 ]; then

	#!/bin/bash

	prompt-to-proceed () {
	read -p "Do you wish to proceed (Press any key to continue or 'n' to exit)? " response
	if [[ $response == 'n' ]] \|\| [[ $response == 'N' ]]; then
	echo " buh-bye"
	echo ""
	exit
	fi
	echo ""