Brian J. Bayer brianjbayer

Adding Rack-Based Health Checks Without curl or wget

Image: Lake View Cemetary, Cleveland OH by Wendy Bayer

You can not address a problem without first knowing that there is a problem. Having health checks in your application allows you to easily determine and monitor the status of your critical application

Representing Email Addresses in Rails

Image: Joshua Tree Saloon by Wendy Bayer

Dealing with and representing email addresses is very common in Ruby on Rails and other web applications. This is especially true when representing and implementing an

Unlocking the Secrets of Rails Secrets and Credentials

If you are like many (most?) of us, you have encountered Rails Credentials/Secrets and secret_key_base and may have been left a bit (or more) confused.

This post is an attempt to remove some of that confusion by

Adding Rails API Error Handling with Tests

Image: Iron Gate by Wendy Bayer

Development is a dangerous game. Things you don't expect, things you do. Systems fail, the cloud is not infallible.

Create, Develop, and Run Your C# (.NET) Projects All in Docker

Image Hand Rail at The Ohio State University by Wendy Bayer

You can create, develop, and run a new C# (.NET) project just using Docker without having to install dotnet on your machine.

An Image-Based Continuous Integration / Continuous Deployment Model

This model and approach is based on the belief that the (Docker) image of the application (and not the source code) should be the "source of truth" and object of the Continuous Integration / Continuous Deployment (CI/CD).

Key Points Covered...

Example of Outputs in GitHub Actions

Called Job

  branch-and-last-commit:
    runs-on: ubuntu-latest
    outputs:
      branch-name: ${{ steps.getbranch.outputs.branchname }}

 steps:

Simple, Cheap Continuous Integration (CI) in a Dockerfile

This is absolutely no substitute for true automated Continuous Integration (CI), but it is better than nothing and it is fairly simple and cheap if you are already building images. It is also a great illustration of how to use multi-stage builds

	# --- Base Image ---
	FROM ruby:3.1.2-slim-bullseye AS ruby-base

	# --- Base Builder Stage ---
	FROM ruby-base AS base-builder

	# Update to match version in app Gemfile.lock
	ARG BUNDLER_VER=2.3.21

	# Static config

	# Dockerfile for a containerized development environment
	# for the railstutorial.org Rails tutorial
	# ASSUMPTION: source is volume mounted
	# docker build --no-cache -t railsgen .
	# docker run -it --rm -v $(pwd):/app -p 3000:3000 railsgen
	# bundle exec bin/rails server -p 3000 -b 0.0.0.0
	FROM ruby:3.1.2-slim-bullseye

	ARG BUNDLER_VER=2.3.14
	ARG RAILS_VER=7.0.4