Missing Disqus template on deployment to gh-pages

[deepakunni3]

This issue was observed by @hmenager after merging PR #149:

Hello, I attempted to merge this year's CoFest PR, but the deployment appears to be failing on GitHub due to a missing Disqus template (https://github.com/OBF/OBF.github.io/actions/runs/24234092151/job/70752255628). I did not modify anything related to this component, and I am not particularly familiar with Hugo or Ruby. If anyone could point me in the right direction to resolve this issue, I would greatly appreciate it!

Looks like this issue was seen last year (#70). Back then, the solution seems to be to:

• use a fixed version of Hugo (which we do)
• use a fixed version of the beautifulhugo template

Looking at the the merged PR (https://github.com/OBF/OBF.github.io/pull/149/changes), it looks like the beautifulhugo submodule was updated as part of the PR.
It may be possible that the theme and hugo was building successfully locally. But it could be that the newer changes in the submodule has introduced the issue since we pin Hugo to an earlier version.

Quickest solution would be to revert the submodule to an earlier state.
CC'ing @gedankenstuecke since you had seen this issue before.

Also, as a side note: would it be better to fork the beautifulhugo theme repo so that we have it in a fixed state (and sync periodically as needed)?

[peterjc]

My understanding from reading #70 is we are pinning hugo (for the CI build) and the theme (via the submolule), which seems pragmatic and stable.

Being a static site generator the security pressure to always have the latest version is reduced.

I don't see what forking the theme would add (over pointing at a specific version), but I also don't know why this has broken. Quoting the error in full:

Run hugo \
Start building sites … 
hugo v0.148.2-40c3d8233d4b123eff74725e5766fc6272f0a84d+extended linux/amd64 BuildDate=2025-07-27T12:43:24Z VendorInfo=gohugoio

Total in 35 ms
Error: error building site: html/template:single.html:94:24: no such template "_internal/disqus.html"

[deepakunni3]

The suggestion to fork the theme repo was to have a specific snapshot of the repository.
This would avoid the issue where a contributor mistakenly updates the submodule to the latest commit (which is typically the intuition when working with submodules).

[gedankenstuecke]

Fixed it by bumping both our version of hugo itself and the version of beautifulhugo. The problem was the partial update/change in #149, which had given us a BH version not compatible with the used version of hugo.

And just updating hugo now wasn't enough either, as the latest hugo version didn't play nice with the used BH version. But now it deploys again 😂

@deepakunni3 in theory we already have "pinned" a version of beautifulhugo, the problem was that #149 did not just edit content but accidentally also bumped the theme version 🙂

[hmenager]

Thanks a million for fixing my mistake @gedankenstuecke ! I was still struggling with it when I realized you had already fixed it! 🙏

[gedankenstuecke]

No worries, there's so many missing parts and it's easy to miss!

[hmenager]

(for the record, I think I understand my mistake: I updated my old local checkout of the website, but back then beautifulhugo wasn't pinned)

[deepakunni3]

Thank you @gedankenstuecke for the quick fix! Glad to hear it was easy to sort out :)

[nlharris]

Yes, HUGE THANKS, Bastian, for fixing this while I slept! 🙏
And thanks as well to Hervé to clearly reporting the problem and Deepak for helping to figure out the problem and propose a solution!
You guys ROCK!