Dev on mrnice.dev

How to add a status page to your Hugo blog

Sun, 17 Sep 2023 22:58:53 +0300

Shortest guide possible, let’s go ⚡️

Setting up a status page

I recommend onlineornot.com.

Take your blog’s URL. For me, that’s https://mrnice.dev.
Create a new check on that URL. Pick “Monitor a website”.

Create a status page, and choose your subdomain. I went with mrnicedev ~> you’ll end up with a URL like https://mrnicedev.onlineornot.com.

You should get something that looks like this:

Adding the status page link to your blog

We’ll do it from the config.toml file (so it’s easy to change) and using a with template statement (so if it’s not set, it won’t show up).

Optimize your Hugo Blog With Unlighthouse

Tue, 16 May 2023 09:36:21 +0300

Recently Google let me see the new Analytics dashboard (they moved from… Something something analytics to something something Analytics 4). And one of they things I saw was that my blog’s performance was bad!

In general the blog’s infrastructure didn’t get much love since I opened it a few years ago, so a cleanup for performance and content is probably in order.

Get initial Lighthouse results

What’s Lighthouse? It’s a tool that Google provides to measure the performance of your site. It’s available as a Chrome extension, but also as a CLI tool that you can run on your site. So I thought that the first order of business was to run Lighthouse on my site and see what I’m getting both for Mobile and Desktop.

Debugging Windows: New Users, Powershell, and TLS

Thu, 26 Dec 2019 15:34:44 +0200

A little context

I wanted to work on this PR in Infection Monkey. Basically, a very simple feature - make the Monkey create a new user, and try to create an HTTPS request as that new user.

Python Server Profiling: A quick guide (with real data)

Fri, 15 Nov 2019 18:04:53 +0200

This post has appeared as an article on issue #2 of PagedOut! magazine.

I improved performance issues in a Python server and survived to tell you the tale.

0) Discover your problem is performance

This can come up via Stress testing ⏱️, User tickets 🎫 or as the underlying cause of other bugs 🐛.

For us, it started with this a demo of the new version of Infection Monkey that had >35 machines. The report generation was so slow, the server just died! Luckily @CyberCaffeinate was able to recognize the situation and relay it to us.