https://www.hjdskes.nl/categories/administration/ Recent content in Administration on Jente Hidskes' website Hugo -- gohugo.io en-us Copyright © 2016-2022 Jente Hidskes Fri, 28 Jun 2019 21:54:19 +0200 https://www.hjdskes.nl/blog/https-update/ Fri, 28 Jun 2019 21:54:19 +0200 https://www.hjdskes.nl/blog/https-update/ For a little over a year now, this website has been enforcing HTTPS over both its www subdomain and the hjdskes.nl apex domain. These certificates are kindly provided automagically by GitHub in a partnership with Let’s Encrypt. In May, the certificate for my website expired. Expecting GitHub to be on top of this, at first I did not take any action. Some of you have reached out to me about the issue, which prompted me to contact GitHub to figure out why my certficate wasn’t being renewed. https://www.hjdskes.nl/blog/github-pgp-response/ Wed, 02 Jan 2019 11:47:43 +0100 https://www.hjdskes.nl/blog/github-pgp-response/ A few weeks ago I wrote about adding a new PGP subkey to your GitHub account. I reported this issue to GitHub when I discovered it. Today, I have gotten a response from GitHub: When a new subkey is added to an existing PGP key on an account, it currently has to be removed and added back to the account to update it on our side. This is expected behaviour for now but I agree it isn’t the most elegant solution! https://www.hjdskes.nl/blog/psa-github-gpg/ Thu, 13 Dec 2018 15:23:39 +0100 https://www.hjdskes.nl/blog/psa-github-gpg/ I not so recently started using subkeys to do my normal PGP work. I made a new subkey specifically for signing things, and naturally wanted to use this new key to sign my commits with git’s builtin GPG support. I picked up my subkey’s ID with gpg --list-keys --keyid-format LONG and set it with git config --global user.signingKey <id>. That’d be it, right? Since you’re reading this, you’ve found out the answer is “no”. https://www.hjdskes.nl/blog/pass/ Wed, 04 Jul 2018 20:47:00 +0200 https://www.hjdskes.nl/blog/pass/ Last week, I received an email from Ticketmaster that my account details may have been leaked through an external supplier. Whilst I did not get notified through Troy Hunt’s excellent Have I Been Pwned?, now was a good a time as any to finally apply some proper password hygiene. A great time, even, as this has been on my to-do list for way too long. I have been preaching proper password hygiene to my family and friends whilst not yet practicing it myself! https://www.hjdskes.nl/blog/https/ Wed, 02 May 2018 11:41:05 +0200 https://www.hjdskes.nl/blog/https/ From today, my website enforces HTTPS again! Github Pages have been supporting HTTPS since June 2016, so when my website was reachable only through hjdskes.github.io I got all of that for free. In fact, because HTTPS is the future(tm), I enabled Github Pages' enforce HTTPS feature in my website’s settings. Since March, my website is also reachable through (www.)hjdskes.nl. When I set this up, I knew I would lose the ability to enforce HTTPS because up until yesterday, Github Pages did not support HTTPS for custom domains. https://www.hjdskes.nl/blog/update-deploying-hugo-on-personal-gh-pages/ Sun, 26 Feb 2017 22:12:00 +0100 https://www.hjdskes.nl/blog/update-deploying-hugo-on-personal-gh-pages/ In my previous post I explained the workflow I use to update this website. It has never been particularly stable, and the process seemed far more complicated than it needed to be. This week I attempted to update the theme of this website. To pull in the theme’s files, I use git submodules. Apparently, this completely break git’s subtrees. I had enough of trying to maintain this complicated setup, so I started looking around for better ways. https://www.hjdskes.nl/blog/deploying-hugo-on-personal-gh-pages/ Tue, 16 Aug 2016 22:07:21 +0200 https://www.hjdskes.nl/blog/deploying-hugo-on-personal-gh-pages/ Hello, World! As this is the first blog post on this website (and indeed, by myself), the introduction had to be done. I’ll leave it at this, though. If you want to know more about me, you can do that here. This website is created using the Hugo static website generator. You define the layout of your pages using regular HTML (combined with Hugo’s templates), CSS and JavaScript and you write your pages' contents using Markdown.