Support self-hosted Commento in Ananke

[220303]

Feature Request: Support self-hosted Commento in Ananke

Background

The Ananke theme currently provides integration with the Commento comment system, but it always uses https://cdn.commento.io/ as the service endpoint.
However, not all users want to rely on the hosted service at commento.io (which is paid). Many users (including myself) prefer to self-host Commento.

---

Problem

Currently, the source file themes/ananke/layouts/partials/commento.html contains the following code:

<div id="commento"></div>
<script defer src="https://cdn.commento.io/js/commento.js"></script>

The Ananke theme always loads Commento from https://cdn.commento.io .
Even if the user configures a commentoUrl parameter in hugo.toml, it will not be read.
As a result, users running their own Commento instance cannot load it on their pages.

---

Expected behavior

Users should be able to specify their own Commento service endpoint in hugo.toml, for example:

commentoEnable = true
commentoUrl = "https://mydomain.com:8080"

Then the blog pages should correctly load the corresponding comment box at the bottom.

---

Proposed implementation

I modified layouts/partials/commento.html to support using the user-defined commentoUrl if provided, and fall back to the default cdn.commento.io otherwise:

{{ if or .Site.Params.commentoEnable .Site.Params.commentoUrl }}
<div id="commento"></div>
<script
  defer
  src="{{ with .Site.Params.commentoUrl }}{{ . }}{{ else }}https://cdn.commento.io{{ end }}/js/commento.js"
></script>
{{ end }}

---

Benefits

• Backward compatible with existing behavior (still supports the default cdn.commento.io).
• Adds support for self-hosted Commento, covering more user scenarios.
• Very small change with minimal maintenance cost.

---

Additional context

I have tested this implementation locally and confirmed that it works as expected.

If the maintainers agree with this approach, I am happy to submit a PR to merge this change into Ananke.

[220303]

I've raised a Pull Request titled "feat: support self-hosted Commento via config param #874".

[davidsneighbour]

That makes sense, but:

There is a method named default in GoHugo. Something like this looks better:

{{ with site.Params.commentoEnable }}
{{ $url := .Site.Params.commentoUrl | compare.Default 'https://cdn.commento.io' }}
<div id="commento"></div>
<script
  defer
  src="{{- $url -}}/js/commento.js"
></script>
{{ end }}

I am not sure how commento.io works; it might make sense to have the full path to commento.js in the configuration (including /js/commento.js) in case that is a movable endpoint.

[220303]

First, in my code, /js/commento.js is appended to the URL in both the custom and default cases.

Note: The final /js/commento.js is written after the end. Hugo templates parse it by concatenating /js/commento.js directly to the output of the entire {{ ... }} expression, so whether with outputs a custom URL or the default URL, /js/commento.js will always be appended at the end.

Next, let's look at the default function you mentioned.

I fully agree with the principle of using Hugo’s built-in functions whenever possible, so I tried your code on my server:

{{ with site.Params.commentoEnable }}
  {{ $url := .Site.Params.commentoUrl | compare.Default 'https://cdn.commento.io' }}
  <div id="commento"></div>
  <script defer src="{{- $url -}}/js/commento.js"></script>
{{ end }}

During the build, it reported an error:

malformed character constant: 'https://cdn.commento.io'

The reason is that in the Go template language, single quotes ' ' are used for single characters, not strings. So writing 'https://cdn.commento.io' directly causes this error.

I changed it to double quotes:

{{ with site.Params.commentoEnable }}
  {{ $url := .Site.Params.commentoUrl | compare.Default "https://cdn.commento.io" }}
  <div id="commento"></div>
  <script defer src="{{- $url -}}/js/commento.js"></script>
{{ end }}

Then a new problem occurred:

can't evaluate field Site in type bool

The reason is that with site.Params.commentoEnable changes the context . to the value of site.Params.commentoEnable (which is a bool), so accessing .Site.Params.commentoUrl inside the with block triggers this error.

The solution is to use if instead:

{{ if site.Params.commentoEnable }}
  {{ $url := site.Params.commentoUrl | compare.Default "https://cdn.commento.io" }}
  <div id="commento"></div>
  <script defer src="{{ $url }}/js/commento.js"></script>
{{ end }}

This allows the site to build correctly and display the comment box.

Finally, after checking the documentation, GoHugo now recommends using default instead of compare.Default, so the final recommended code is:

{{ if site.Params.commentoEnable }}
  {{ $url := site.Params.commentoUrl | default "https://cdn.commento.io" }}
  <div id="commento"></div>
  <script defer src="{{ $url }}/js/commento.js"></script>
{{ end }}

I have verified that this code works perfectly.

You can see the effect as shown above at http://220303.work/cs/rocky-linux-+-nginx-+-hugo-+-go-静态博客网站搭建 .

I have closed the previous PR, and if you like, I can open a new PR including this updated code.