In my previous article, I set up a Kubernetes cluster with hosting, ingress, and TLS. This time my goal was to deploy a private Docker registry on the cluster. Then upload an image to the registry and deploy it on the cluster.
Again, there's documentation on how to do that via DigitalOcean. This was my starting point, and I made a few adjustments along the way.
DNS My first task was setting up another A record to point to the cluster.
This article describes my experience re-hosting this site on DigitalOcean with Kubernetes. If you've read my previous posts, you know this site is staticly generated with Hugo. I deploy using Git on Azure App Services. As I move deeper into total containerization, I've started looking for a host that's more tailored for many small containers.
Although I enjoy App Services for their simplicity, I've run into publishing issues when using Docker.
Winter made me a little stir-crazy. In order to deflect the brain spirals, I wanted to make a little side project. It breaks my current cycle while feeling happy I accomplished something. I placed tight time constraints to ensure I'd complete it.
Put in a URL that you'd like to hide. Enter the meta information you'd like to display on sites that show previews (like Slack). When you submit the form a new link will be generated with a copy function.
Git is widely adopted by the development community. However, some developer's haven't gotten to cut their teeth with it for various reasons. This article is designed to help people get started using Git for the first time.
This article uses the command line to work with Git. Although GUIs exist, I found it helpful to learn the concepts through the command line. If you aren't comfortable with the command line djangogirls.
Back in 2017 I converted this site to Hugo. I did it to control my content while checking out some static site generators. At the time I was interested in just getting the site up and running. To aid in that process I quickly grabbed a theme on the Hugo theme website and started porting content. Fast forward a year, and now I'm looking to give a little more love to the site.
In a previous article I wrote about using middleware to add concurrency keys into an Asp.Net Core project. I'd like to extend that and show how to integrate a logging platform with concurrency keys. Our .Net Core logging framework of choice is Serilog. They have great integration with common logging protocols, and there stuff is very extensible.
Logging with Serilog Serilog allows a developer to inject properties into the LogContext. The LogContext This allows us to take properties and map them to the log templates.
There are a few ways to create a Swagger client in .Net. For native Visual Studio users you can right-click on a project and generate them for the .Net Framework. However, I was looking for a way to consistantly generate a cross-platform client. Enter Autorest.
In this article I'll show how to create a Swagger-enabled .Net Core Api, and the build a cross-platform .Net client library that works in both .
Who doesn't like a cool looking console? It reminds me of my old Gentoo / Enlightenment days. Previously, I used Console2 to pretty up my Windows console, but they don't seem to be updating it anymore. Luckily, there is a fork out there being updated with better rendering and new features.
Downloading ConzoleZ You can quickly download the latest release here. Make sure you pick the correct build (x86/x64). Once downloaded, extract the contents wherever you would like including all the dlls and executables that come bundled in.
When I put up a new website in Azure I tend to run into the same problems. Pointing DNS to the azure website nets a lot of urls. I'll have mydomain.com, www.mydomain.com, mydomain.azurewebsites.net, and http/https versions of all of them. When talking SEO, you generally don't want duplicate ways to get to the same content. Luckily, this can be solved relatively painlessly with url rewrites in the web.config. I put together a quick reference to handle some of the scenarios.
I'm recently working with microservices in Asp.Net Core. With microservices, there tends to be a lot of network connectivity. One service potentially calls many other services to build a final response. It's difficult to see where a request started, all the subsequent requests that happened back to the final result. Concurrency keys are a way to track a single request through all its dependancies.
The idea is when a request is made a concurrency key is generated.