Skip to main content

Posts tagged with #100 days to offload

Recent Posts (Page 4)

Photo by Todd Quackenbush via Unsplash

Notes from the Laboratory: July 2023

I am trying this new “thing” of “reporting” what I was up to in a certain period this year, and monthly reviews just sound like something normal people would do. Bear with me while I am typing up this report.

Photo by Fikret tozak via Unsplash

WordPress Drops PHP 5

The WordPress blog announced on July 6th that starting from the next release (WP 6.3 on August 8th, 2023), the CMS will no longer support PHP 5. Yes, that’s correct. PHP 5.6, the final version of PHP 5, reached the end of its lifecycle on December 31st, 2018, but it was still supported by the most widely used CMS until recently.

Photo by Henry & Co. via Unsplash

Removing all local and remote tags in Git

Every now and then I find myself in the situation of needing to tidy up my projects and remove large amounts of local and remote tags in my Git repositories. The procedure is not too hard, but I have to look it up again each time, so why not just writing it up.

Photo by Todd Quackenbush via Unsplash

Notes from the Laboratory: June 2023

It’s that time of the month again where I am trying this “new thing” of “reporting” what I was up to in a certain time period this year. So bear with me while I am typing up this report. 100DaysToOffload: I recently realised, that theoretically this whole 100 posts in one year thingy here on the blog is going on for 1.

Photo by Pascal Meier via Unsplash

Ping Goes Poof

Google on Monday announced that they will change several things regarding to sitemaps and pinging the search engine about updates of the sitemap. The main points are: Pings are not accepted anymore starting in 6 months, due to them being unreliable.

Photo by Vincent van Zalinge via Unsplash

Changes to Hugo’s debugging abilities on the CLI

Hugo in version 0.114.0 finally introduced the changes I wrote about a while back. The hugo command on the CLI now dropped the –log and –verboseLog flags and deprecated the –verbose and –debug flags. Instead, it now uses the –logLevel as an indicator of verbosity.

Choose a key

How to handle key issues with apt on Ubuntu

For some time now, I was receiving the following warnings after an otherwise successful run of apt update: plain COPY 1W: http://linux.dropbox.com/ubuntu/dists/disco/Release.gpg: 2Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), 3see the DEPRECATION section in apt-key(8) for details. 4W: http://prerelease.keybase.io/deb/dists/stable/InRelease: 5Key is stored in legacy trusted.

Back to top
Back Forward