I am now Azure certified, I passed my AZ-104 cert a few weeks ago. I’ve been using both Azure and AWS for years now, and wanted to sit down and actually get certified. On my list next would be the Azure Architect cert and then move on to getting my AWS certs. You can view my badge here

Another quick one. So I just learned about a new feature in Docker Desktop in which Docker Desktop can create a Dockerfile just by examining the code in your directory tree, which is pretty cool, so I updated my version of Docker Desktop to take advantage of this new feature, and it re-enforced my belief that Devs should not manually create Dockerfiles. Let’s have a look at the output from the command docker init # syntax=docker/dockerfile:1 # Comments are provided throughout this file to help you get started.

So I’ve run into this error everytime I’ve cloned my site or pretty much any Hugo template, but it was really annoying for me when it comes to my personal blog, I would clone my private git repo and try to build my site and I would see the below error message WARN 2024/02/06 07:26:21 found no layout file for "html" for kind "page": You should create a template file which matches Hugo Layouts Lookup Rules for this combination.

HAPPY NEW YEAR!!! to all, I will try and post more in 2024!

I moved fabianbrash.com from running on DOKS to running inside of an s3 bucket fronted by cloudfront, but why? Simple cost. DO has a great k8s offering but their last round of price increases meant that I would now be paying over $90/month for 3 small k8s nodes, and even with the fact that I deployed other APPS into the cluster, I just couldn’t justify the cost, so I switched. I am also going to look into how to host other APPS I make in the future, I do have access to internal k8s clusters, but I have no interest in opening those up to the outside world and deal with the security risks that come with that.

I’ve passed my CKA!!!

So I ran into an issue today, I was deploying TAP on a TKGm cluster on-prem and I went with one of the available t-shirt sizes for my nodes — After I deployed TAP I noticed that the buildservice kept failing so I started to do a little troubleshooting, and when I checked the events I noticed that their were errors regarding disk pressure on the nodes and the pods being evicted, and then I remembered that TAP requires a minimum of 70GB of disk space on the worker nodes and I only had 40GB.

So at my new job I’ve been learning TAP(Tanzu Application Platform) and as apart of that I’ve had to setup a domain so I can build new apps and serve them from that domain, so obviously I just picked a domain from a list of domains that I own, and the domain I chose was alexanderbrash.dev; simple enough, but then I noticed that when I tried to access the TAP GUI in Chrome or Firefox I was getting redirected to the https version of the site and of course I hadn’t setup any certs or anything I was just messing around, even if I used an incognito window or tab, same thing, every time I would go to http://tap-gui.

So I just had to renew my letsencrypt certificate for my VCSA and ran into a few issues and I wanted to write them down here, so I will go through creating the cert and adding it to your VCSA in the below blog post. I will assume you have certbot only installed on your machine Let’s create our cert certbot certonly -d myservice.domain.com --manual --preferred-challenges dns --agree-tos -m mail@mail.com Of course make changes as needed from the above command, then follow the instructions to add a TXT record to your DNS provider Now comes the tricky bit of assemblying the certificate in a way that your VCSA will accept it and not choke, the below blog helped out quite a bit.

It’s been a while since I’ve posted on here but I’ve been quite busy, I’ve started to study for my CKA, plus I’ve been doing some React/Next.js/Redux work. I’ve built a couple of apps and I’m hosting them on Vercel check them out below. Hulu 2.0 Tesla Clone I hope to add some more to the above list, one app I’m thinking about is building a crypto bank app using Next.