Continuous Coffee Brewing

Intro/Backstory

Like any recipe website, this is relevant for context, but ultimately you’ll want to skip to the next heading if you only want to know how I made WSL 2 work better on Windows

Recently I’ve acquired a regular T470 that thankfully still had a working Thunderbolt 3 port, and put my main laptop install of Arch on there.

It was good for a time even with it’s i5-7300U meaning I couldn’t run some VM workloads on my laptop the same as before.

Continue reading 

A while back I setup Drone-CI for some internal projects I run at my house to simplify image builds & testing for the various personal projects I maintain

Shortly after I realized that Drone-CI 2 wasn’t really free as I assumed it was, after about 5000 builds it will complain about the “free trial license” being exceeded and to continue running it means compiling and building it manually with atleast the nolimit tag

Continue reading 

Backstory (Skip if you don’t like my usual rambling)

One of the fun aspects I get to handle at work is when a new user is onboarded on the web team I get to generate some SSH keys for said user and authorize it across our fleet of internal servers and customer servers

While it wasn’t impossible, I had to keep a decent list of every server we had access to and ensure I kept a good list of who was authorized for where, and hope I don’t accidentally break the ~/.ssh/authorized_keys file with a bad copy/paste

Continue reading 

Background: My Main Desktop

Those of you who have read my About page know I like to keep what computers I use up to date in there. Well my current Ryzen 9 3950x rig in there started out as my Ryzen 1800x rig back in 2017 as a windows box due to the C-State problems linux had with first gen Ryzen. Eventually I figured it out and swapped my desktop from Windows to Manjaro back in mid 2019.

Continue reading 

Background Info

Over the last year I’ve been working more with ansible, I’ve even used IronicBadger’s Infra playbook as a base to my own personal infrastructure playbook.

However one problem that has come up recently was with the release of docker-compose 2.0 because it was rewritten in go.

Don’t get me wrong, so far the go version of docker-compose has been fantastic, it appears to be faster to run and I love the changes they have done to the terminal output.

Continue reading 

Docker pipeline streamlining and how to setup your own private GitLab runners

Hey guys, it’s been a while. Over the last number of months with the Covid-19 pandemic going on I’ve been focusing heavily on docker container building and cluster orchestration both professionally and personally.

Anyways this is an update to my first post on this blog from about 6 months ago.

First up will be setting up your own GitLab-ci runner that you can register to your own private group, a specific project, or setting it up as a shared runner on your own private GitLab instance.

Continue reading 

Using Docker to easily generate a Hexo blog writing environment

Some of you have probably noticed that this blog is generated through Hexo.
Right now it’s a blog using Cactus as it’s theme

Edit: Used to be Hexo, now it’s generated through Hugo and the Ficurinia theme

It’s super simple and easy for me to maintain.

However the main issue I have is that I swap computers all the time.

I have about 3 computers I swap with constantly. these are my:

Continue reading 

Continuous Docker Image Delivery with GitLab-CI, Docker-in-Docker, and TLS

One of the first things I had to sort out was building in gitlab-ci with docker.

Hard to make custom containers in a timely fashion if they have to be built every time you move between environments.

This will work by default with Gitlab’s shared runners out of the box.

If your using your own shared runners, there is some special setup required to get that to work. (Keep an eye out for a post on setting that up)
EDIT: Go to the follow up post to read up on how to do this

Continue reading 