Infrastructure

Guilhem Moulin wrote in #note-2:

and how can I deploy the new static website?

I suggest that I deploy a new CD pipeline for that (like we have for TDF's and other production Hugo-based sites). That way any push to the default branch automatically makes it to production.

Did that now, but generation fails:

WARN Module "libocon-latam-2024" is not compatible with this Hugo version; run "hugo mod graph" for more information.
Start building sites …
[…]
ERROR render of "home" failed: "…/themes/libocon-latam-2024/layouts/_default/baseof.html:2:18": execute of template failed: template: _default/home.html:2:18: executing "_default/home.html" at <site>: can't evaluate field LanguageCode in type *langs.Language
ERROR render of "taxonomy" failed: "…/themes/libocon-latam-2024/layouts/_default/baseof.html:2:18": execute of template failed: template: _default/list.html:2:18: executing "_default/list.html" at <site>: can't evaluate field LanguageCode in type *langs.Language
ERROR render of "section" failed: "…/themes/libocon-latam-2024/layouts/_default/baseof.html:2:18": execute of template failed: template: _default/list.html:2:18: executing "_default/list.html" at <site>: can't evaluate field LanguageCode in type *langs.Language
ERROR render of "taxonomy" failed: "…/themes/libocon-latam-2024/layouts/_default/baseof.html:2:18": execute of template failed: template: _default/list.html:2:18: executing "_default/list.html" at <site>: can't evaluate field LanguageCode in type *langs.Language
Error: Error building site: failed to render pages: render of "page" failed: "…/themes/libocon-latam-2024/layouts/_default/baseof.html:2:18": execute of template failed: template: _default/single.html:2:18: executing "_default/single.html" at <site>: can't evaluate field LanguageCode in type *langs.Language

Which Hugo version are you using in development? Ideally the site shouldn't use any feature introduced after version v0.111.3 (i.e. current Debian stable).

I haven't changed the DNS records yet.

Thank you Guilhem

I did the changes to run it with that specific version. It should work now.

Can we wait pointing the DNS for a bit, I need to update the text first

No problem, just let me know when to make the switch. In the meantime I lowered the TTL of the existing record to speed up the transition.

Hugo v111.3 still shows the following warning

Module "libocon-latam-2024" is not compatible with this Hugo version; run "hugo mod graph" for more information.

but it looks like it's not fatal, at least it's able to built the site now. You can see how it looks like by pointing the hostname to 65.109.131.19 on your local resolver (for instance by editing /etc/hosts).

Hi Guilhem,

The site is ready to be deployed