Infrastructure Docs Startpage

Infrastructure repository with configs and docs for my local workstations, my homelab with tool server and RasPi nodes and my public cloud-hosted website.

Github Badge Github Badge

Requirements Overview


  1. Centrally manage all my infrastructure components.

Quality Goals

  1. Run test, scans and validations automatically with Github Actions

    1. Everything inside this repo is linted and validated

    2. Docker builds are tested regularly

    3. Container images are scanned for vulerabilities

  2. Encapsulate as much as possible inside Docker Containers and/or Vagrantboxes to ensure (broken) updates can easily be rolled back and the setup is portable in case I have to reset my workstation or have to switch to another workstation.

    1. Add or update packages without any risk → avoid having to repair broken installations (dumping the broken setup and reverting to a working one is preferred).

    2. Instead of using e.g. apt-get install, use Docker Containers and create a Symlink in /usr/bin to a wrapper-script which delegates commands to a Docker container.

Technologies used in this project

The following technologies are the big building blocks of this project. Other technologies and helpers like several linters although being useful and essential as well don’t qualify as building block technologies and are not listed here.

Technology Purpose Website


Provisioning and configuration for server nodes (physical, virtual and RasPi) on my homelab

Asciidoc & Antora

Docs as Code for this project &

Bash scripts

Automate installations, wrap commands into repeatable scripts, utilities, etc.


Docker & Docker Compose

Run containers on on my local workstation and in Vagrantboxes &


Provision Cloud Infrastructure and local services on my toolserver

Vagrant & Virtualbox

Virtual machines

Github Settings

Protect main branch by checking "Require status checks to pass before merging" and "Require branches to be up to date before merging" in Settings > Branches > main for each repo.

Gitpod Settings

Configure envorinment variables for all Gitpod worpspaces at

Variable Value Scope Info




Log level (used for console outputs)




Log level (used for console outputs)




Log level (used for console outputs)




Log level (used for console outputs)




Yellow text




Pink text




Text in default color (white)

DockerHub Settings

  1. Go to " → Account Settings → Security" and set up an Access Token to use with Github Actions.

  2. Go to "repository "infrastructure" on → Settings → Secrets → Actions and add two secrets to log in to DockerHub from a Github Actions pipeline

    1. DOCKERHUB_USER = sommerfeldio


Container Scanning with Snyk

In order to use the Snyk Action you will need to have a Snyk API token. More details in or you can signup for free at

  1. Create a SNYK_TOKEN secret in Github the same way you created the DockerHub secrets.

Snyk can be used to break the build when it detects vulnerabilities. In this case we want to continue-on-error: true to upload the issues to GitHub Code Scanning.

Integrate Slack with Github Actions

Some pipelines send their build status and sometimes other messages to slack.

  1. For custom messsages use action slack-send → Technique 2: Slack App.This creates (among other things) the SLACK_BOT_TOKEN secret.

    1. Direct Link to Slack App Management Console =

  2. For build status messages use