MandarisThis post is a bit of a ramble and more for documenting my thinking.
Things have been kind of hectic in my personal life and I’ve been taking a step away from creating and interacting. In the time that I’ve been away
, there have been changes to Hugo and the Micro.blog. In some ways, it’s been a relief that Micro.blog is using v0.117. Other than the changes in v0.132 (The introduction of alerts although v0.140 and v0.142 has some significant fixes to this), I haven’t really seen anything catches my interest.
Still, I have seen some interesting things being done with blogs and want to be able to take advantage of the newer versions of Hugo when Manton and crew make it available.
I thought I would document what steps I went through. I’ve begun writing this on September 24th and worked on it in my spare time until clicking the publish button.
Environmental Setup
At the beginning of this process, I had Hugo v0.146.3 installed on my MacBook Air running Tahoe 26.1. I want to be able to test in different versions of Hugo so did a search and found several article pointing to hvm (Hugo Version Manager). The tool was created by Joe Mooring who is very active on the Hugo Forums and you can go to the GitHub repository to review the code.
The first thing I did was use Kostas’ instructions for using brew to get a certain version of running a specific version of Hugo and then I downloaded the v.117 hugo ruby installer.
That didn’t work.
So, I downloaded the homebrew-core from the GitHub repository and then changing to the commit that has the version I want.
git checkout e243fd4
That didn’t work for me as well and I grew tired of trying to find the right combinations of brew commands.
So, I followed the directions and ran the next step to see an error
mandaris@skylite ~ % hvm gen alias --help
zsh: command not found: hvm
That’s when I realized that my system is almost a clean install other than the installation of the command line tools and brew, I didn’t have things like /usr/local/bin or anything else that I had taken from granted in my previous setup.
I set up oh-my-zsh and kept the defaults. I forgot why I use this but not how. I added the following to my .zshrc
export PATH=$PATH:$(go env GOPATH)/bin
Then new shell instances will be able to find the executables from GO.
➜ ~ which hvm
/Users/mandaris/go/bin/hvm
When I ran it the first time, I didn’t see my option and asked on the forums before I went through the associated documents to see that I could add the specific version to a .hvm file that I can put in the root of the folder I’m working with.
➜ local-hugo hvm status
The current directory is configured to use Hugo v0.117.0.
Cached versions of the Hugo executable:
v0.151.0
v0.117.0
Now I’m able to switch between the versions easily.
The only problem is that some of the plugins that I use locally are not compatible with that version. For example, the stoot plugin to embed mastodon post.
Hashtag Goals
Other than the work to keep the theme ready for newer versions of Hugo, I’ve identified a couple other things that I want to work on.
- Increase the performance of the site
I don’t want to remove styling or minimize the file because I feel that it will help others learn and I’m too afraid tokill my darlings
. - Move the About me to the bottom
I feel having it on the side on larger screens draws focus away from the writing on page.
In addition, I have to figure out why @view-transition doesn’t work on the server but works on my local copy of the site.
The goal is to get this all finished before Thanksgiving break. So if you’re reading this please feel free to bug me about it as my self imposed deadline draws near.
Take Care!
