1.1 Documentation

State/Version: 20230829p1

Table of contents

Skip the “Deep Dive” sections for a brief fly over.

1.1 About the author

  • Senor Linux System Administrator, Cluster Operator (automate provision and configuration of clusters), Platform Engineer (build continuous delivery for developer teams) and HomeLab enthusiast
  • Daily business: #devops #kubernetes #openshift #gitops #ansible
  • Current place of residence: Berlin (Germany)

1.2 About this blog

  • This blog is built with hugo.

1.2.1 Creation process

This section describes the ci/cd workflow that creates the gerundium.github.io blog.

1.2.1.1 Creation workflow

  1. Create content offline (braindump).
  2. Commit and push code changes, that are considered source code, to blog-source@github.

    That event will not trigger any pipeline.

    Source code changes include manual changes to any directory except “/public”

  3. Commit and push code changes, that are considered public blog, to blog-source@github.

    That event will trigger the github actions pipeline.

    Public blog changes contain changes that are made to “/public” directory by executing “hugo” command

FlowChart

flowchart LR 0 -->|Push| A A -->|Push| B

  • 0) Laptop - private, local clone of blog-source@github
  • A) blog-source@github - private, contains full hugo code
  • B) blog-rendered@github - public, contains static (rendered) hugo html code