Remark42 on Kliku Kliku

remark42 in Hugo: a cross-domain session without third-party cookies

Fri, 24 Jul 2026 00:00:00 +0000

Introduction

This is another post in the series about comment systems for Hugo. In the previous one I set up the remark42 app itself on a VPS alongside the existing caddy-docker-proxy: Self-hosting remark42 alongside an existing Caddy on a VPS . The backend replies “pong”, the BoltDB database accepts writes. But those aren’t yet comments under posts. For them to appear on the page you need to wire in the widget: a piece of JavaScript that causes an iframe with a thread list and a form to be created.

remark42: GitHub OAuth and email notifications via transactional SMTP

Fri, 17 Jul 2026 00:00:00 +0000

Introduction

In Self-hosting remark42 alongside an existing Caddy on VPS I set up a remark42 instance with a minimal configuration. The container runs, the widget embeds on the blog, everyone can comment as anonymous. The starter setup is functional enough to prove something works, but it has two gaps that show up on day one of real use: no meaningful authentication and no notifications of any kind, which means a new comment can only be noticed by manually visiting posts.

Self-hosting remark42 alongside an existing Caddy on VPS

Fri, 10 Jul 2026 00:00:00 +0000

Introduction

I’m continuing the series reviewing comment systems for Hugo. After Self-hosting Cusdis with Caddy on VPS it’s time for remark42 . Unlike Cusdis (which has a managed version at cusdis.com) and Disqus (which is SaaS only), remark42 does not offer a managed variant. The only path is self-hosting. If you want to try remark42 at all, this post covers exactly that setup.

The setup from the previous post has grown since then. To the Caddy dedicated to Cusdis (configured via a Caddyfile, ports 80/443 on the host) I added several more services. Each one had to be appended to that same Caddyfile, which grew tedious and typo-prone with more entries. So I switched to lucaslorentz/caddy-docker-proxy : a single Caddy instance that builds its proxy configuration from Docker labels on the containers. Cusdis was migrated onto this pattern too.