The last post here is dated February 18, 2021. It was a perfectly ordinary how-to about Bitbucket permissions, and nothing about it suggested it would be the last one for five and a half years. There was no farewell post, no “taking a break” announcement. The blog just — stopped.
This post is the missing announcement, written from the other side.
What happened # The short version: life kept running, and the writing habit didn’t.
Time to make checkpoint number 1 - it is day 11 of 30.
So far - out of this 11 days I have 10 days with commits. The missing day was fully dedicated to working on presentation and documentation, that unfortunately ends up Confluence and Google Doc, not in some proper textual format (read: Markdown or RestructuredText) backed by a repository.
Stuff that I worked on:
some minor updates to resume (added AWS badges, fixed some typos) notes from certification courses + code fragments scripts for automation of documents / ebooks backup from iCloud to local drives Most commits went to documentation / practice code for my project “Many ways to Kubernetes” where I play with building up K8s clusters using different approaches. So far I did the “Kubernetes the hard way” - following the course from Linux Academy (https://linuxacademy.com/cp/modules/view/id/221),
My work in last few years took my away from practical coding towards DevOps. Despite the increased role of IaaC in our DevOps, this often means living in iTerm and AWS console with interaction not being captured in any form.
On writing side, lots of my output shifted from code towards writing text in Wiki’s, GoogleDocs and more and more in Slack messages. The code I write are short one-liners or small scripts with very short life span. This makes me a bit sad as there is no sense of accomplishment at the end of the day or week. The git log does not work over Wiki, AWS console, iTerm, Slack and GoogleDrive.
Today’s blog of the day is a special one. It does not deal with cloud, DevOps or distributed systems. The theme of the blog is travel, life of digital nomad and observations on life from a perspective of a smart young woman, working as Online English teacher and travelling a lot while doing so - https://bookandtravel.blog/
What makes this blog dear and interesting to me is that it’s author is my daughter Silvia. What could make the blog interesting and valuable for other audience (especially those learning English who are interested in personal development) is the format of the entries - as they combine reading and language teaching. Each post contains 10-20 emphasized words or expressions that are explained in footnotes - check this one
Parallel building challenges # Unlike Github, Gitlab considers Hugo blogs first class citizens and does not impose any restrictions on repo naming.
I had 3 challenges to overcome related to co-existence of GH and GL versions:
I need to use same repo for both GH and GL the submodule link for public does not work on GL the site root is different - I have no custom domain forward for GitLab Using same repo # To separate the GH and GL, I have added 2 remotes to repo and special branch gitlab-pages.
How does the blog setup and publishing work # Before I forget, here is how the current configuration works.
There are two repositories at play:
source repo - https://github.com/miroadamy/miroadamy.com github pages repo (== GHPR) - https://github.com/miroadamy/miroadamy.github.io The blog source repo contains only source files (.md, static media etc). This repo has usual submodules under the /themes - e.g. /themes/even which is one currently used.
I have decided to consolidate all piecemeal versions of my blogpost uder one roof and at the same to do these four things
technology upgrade - from Jekyll to Hugo visual refresh of the page review tagging and categorization merge hidden posts from Wikis to one place Why Hugo replaced Jekyll # The version 3 of my blog (see below for a bit of history) has been hosted on Github pages and using the default static site generators - Jekyll.
That is what I do - jump from project to project to topic to project. And back.
It is uncertain how good is all this - but as they say:
“If you cannot do something right, learn to enjoy doing it poorly”
As part of “back to basics” software minimalism movement, I have exported the old Wordpress blog and loaded it into Jekyll with intention to publish it on my Github
This contains almost 10 years worth of history of my posts, plus few not yet previously unpublished posts.
It is based on Jekyll Clean theme, created by Scott Emmons - see it / get it from github.
If you are interested in the Jekyll Clean theme:
The continuation of the old Wordpress blog with more agreeable tools: Github Wiki + Gollum, Markdown and Git.
My old blog at Miro’s World has been kinda neglected in last two years. I have written several entries and published them only internally. I have decided now to pull those of the entries that do not contain customer references, code or customer IP out.