Spent way too long last night debugging why my custom 404 page worked locally but not in production on my new Hugo site.

The fix was a simple .htaccess file with one line:
ErrorDocument 404 /404.html

Server configuration is clearly not my forte.

#blogging #devlife #androiddev #gohugoio

Made my first little contribution to @gohugoio documentation yesterday! It's about installing #dartsass in the CI workflow on #Sourcehut Builds, which I'm using to deploy my Hugo site to my static host of choice: Bunny.net.

(libsass is deprecated in Hugo)

I learnt a bit more Git during the pull request too—about rebasing, but I'm still not very good at it (merging the changes is a bit confusing to me).

The actual docs page: https://gohugo.io/host-and-deploy/host-on-sourcehut-pages/

#gohugoio #gohugo #Hugo #CICD #srht

Update aus dem Maschinenraum:

Winterzeit bedeutet Maintenance Zeit. 👨‍🔧
In diesem Sinne wurde gerade das #relearn Template, auf git submodule umgestellt und die #gohugoio version aktualisiert. Der Prozess ist noch nicht abgeschlossen, aber für den Moment läuft alles.

Falls jemand etwas auffallen sollte, dann gerne melden.
https://github.com/davidbeckonline/pegel-konstanz_website

Insgesamt überlege ich von AWS Amplify auf #codebergpages umzustellen. Aber das ist noch nicht stabil. Insofern will ich das erst einmal testen.

Release v0.150.0 · #gohugoio/hugo

https://github.com/gohugoio/hugo/releases/tag/v0.150.0

Just posted another blog post, touching on mental health and the move of my site to a new static site generator.

https://tim-harrison.uk/posts/sixth-post/

#gohugoio
#codebergpages

Hugo site generator users, be aware of a breaking change in v0.128.2.

I hadn't written a blog post in a while, and when I started preparing a new one using a current Hugo version (v0131.0), I suddenly got errors that did not seem to make sense to me, especially as they occurred on articles I hadn't changed for months or even years:

ERROR [en] REF_NOT_FOUND: Ref "/bintree": "/.../Blog/Hugo/content/post/big-o/index.md:66:65": page not found
ERROR [en] REF_NOT_FOUND: Ref "/balancedtree/": "/.../Blog/Hugo/content/post/big-o/index.md:66:108": page not found
ERROR [en] REF_NOT_FOUND: Ref "/flow/": "/.../Blog/Hugo/content/post/flow2go/index.md:25:24": page not found

...and a dozen more.

The pages obviously were there, so what had changed?

I have a permalink mapping in place that maps all articles that live in the content/post/ folder to the top level. That is, instead of /post/bintree, the article appears as /bintree on the site:

post = "/:filename/"

The cross-references I used were pointing to the published slug:

{{< ref "/bintree" >}})

This worked well until a change in v0.128.2 that disabled short lookups for paths with leading slash (apparently because these were considered a bug).

Thanks to the help of the generous Hugo community, I was finally able to pin down the cause of my issue to this change. (But it still had cost me a couple of hours of inspecting configs, building older Hugo releases to compare behavior, etc.)

To eliminate the errors, I changed all cross-references to include the /post/ prefix, like so:

{{< ref "/post/bintree" >}})

So, if you use permalinks configurations like the above to shorten the slug, AND if your cross-references point to the published slug rather than the internal content path, you now know how to fix the resulting errors.

#hugo #gohugo #gohugoio

Thank you to everyone who joined us at #HugoConf2023 🎊

Fantastic to see the #GoHugoIO community come together 🐝

Keep an eye out for all this year’s talks & workshops to be posted on https://hugoconf.io/ 🤩

🥳 That’s a wrap on #HugoConf2023! 🥳

Join @cloudcannon’s Mike Neumegen & #HugoConf co-organizer @avidlarge for final remarks and questions, live in 30 minutes: https://www.youtube.com/watch?v=OTclpTZq-S4

Thanks #GoHugoIO community 🐝 you make HugoConf so special!