rewrote parts of the ssl checker blog post, update meta info, makefile and devcontainer

Author: CoderWithAttitude

.devcontainer/devcontainer.json

@@ -1,28 +1,15 @@
 {
   "name": "jekyll",
-  //"dockerfile": "Dockerfile",
   "dockerComposeFile": [
     "docker-compose.yml"
   ],
-  // Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile
-  //"image": "mcr.microsoft.com/devcontainers/jekyll:0-bullseye",
-  // Features to add to the dev container. More info: https://containers.dev/features.
-  /*"mounts": [
-    "source=${localEnv:HOME}${localEnv:USERPROFILE},target=/host-home-folder,type=bind,consistency=cached",
-    "source=${localWorkspaceFolder},target=/data,type=bind,consistency=cached"
-  ],*/
-  // Use 'forwardPorts' to make a list of ports inside the container available locally.
   "forwardPorts": [
     // Jekyll server
     4000,
     // Live reload server
     35729
   ],
-  // Use 'postCreateCommand' to run commands after the container is created.
-  //"postCreateCommand": "sh .devcontainer/post-create.sh",
   "postCreateCommand": "bundle install --verbose",
-  //"postStartCommand": "bundle exec jekyll serve --baseurl=\"\"",
-  //"postStartCommand": "bundle exec jekyll serve --host=0.0.0.0 --livereload --baseurl=\"\"",
   "customizations": {
     "vscode": {
       "extensions": [
@@ -32,16 +19,13 @@
         "google.geminicodeassist",
         "streetsidesoftware.code-spell-checker-german",
         "streetsidesoftware.code-spell-checker-canadian-english",
+        "streetsidesoftware.code-spell-checker",
         "DavidAnson.vscode-markdownlint"
       ]
     }
   },
   "service": "jekyll",
   "workspaceFolder": "/site",
-  // Configure tool-specific properties.
-  // "customizations": {},
-  // Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root.
-  // "remoteUser": "root"
-  //"remoteUser": "vscode"
+  "postStartCommand": "make serve",
   "shutdownAction": "stopCompose"
 }

Makefile

@@ -1,8 +1,14 @@
-install:
+bundler:
+	gem install bundler:4.0.1
+install: bundler
 	bundle install
 verify:
 	bundle exec jekyll --version
-build: install 
-	bundle exec jekyll build
-serve: build
-	bundle exec jekyll serve --host 0.0.0.0 --port 4000 --livereload
+serve: install
+	bundle exec jekyll serve --host 0.0.0.0 --port 4000 --livereload
+# these targets can be used to test the running setup
+curl_local:
+	curl http://localhost:4000
+curl_host:
+	curl http://host.docker.internal:4040
+.PHONY: bundler install verify serve curl_local curl_host

_config.yml

@@ -19,13 +19,14 @@ title: C.W.A. - Coder with Attitude
 #  Write an awesome description for your new site here. You can edit this
 #  line in _config.yml. It will appear in your document head meta (for
 #  Google search results) and in your feed.xml site description.
-description: Talk is cheap - Show me the code (config) #>-
+description: Talk is cheap - Show me the code #>-
 
 baseurl: "" # the subpath of your site, e.g. /blog
 url: "https://www.volker-benders.de" # the base hostname & protocol for your site, e.g. http://example.com
 twitter_username: JavaVolker
 github_username:  CWACoderWithAttitude
 linkedin_username: volkerbenders
+resume_website_url: "https://www.volker-benders.de/resume"
 author: Volker
 # Build settings
 markdown: kramdown

_posts/2025-07-20-check-ssl-certs.markdown

@@ -6,10 +6,21 @@ categories: [web]
 tags: [ssl, cert, expired, valid]
 ---
 
-# The problem
-Our solution to issue, administer and maintain certificates for SSL encryption had to be updated.
+# TL;DR
+SSL Cert Checker lets you check the validity for a bunch of endpoints
 
-The transition process was quite challenging. The number of involved certs and application using them was humongous.
+## Problem
+
+Our previous CA software had reached EOL. 
+
+So we had to setup a new one and incrementally rollout new certs to application. During transition time two valid certs were used: old certs issued by trhe legacy CA. And new certs issued by the new CA software.
+
+To assist ensuring all apps have valid certs i designed a small tool.
+This tool enabled us to see which apps already use new certs and which ones need attention.
+
+## Challenge
+
+The number of involved certs and applications using them was humongous.
 
 Every service and application was documented in excel.