Add a status canary hidden string #170

Merged
stb merged 3 commits from status-canary into main 2026-06-19 08:55:30 +02:00
Owner

This allows status.hamburg.ccc.de to work irrespective of actual content changes.

This allows status.hamburg.ccc.de to work irrespective of actual content changes.
Add a status canary hidden string
Some checks failed
/ build (pull_request) Failing after 2m31s
d63fc21d32
This allows status.hamburg.ccc.de to work irrespective of actual content changes.
stb requested review from june 2026-06-15 19:15:53 +02:00
stb scheduled this pull request to auto merge when all checks succeed 2026-06-15 19:15:57 +02:00
Encode domain in canary
Some checks failed
/ build (pull_request) Failing after 16m4s
9b5017c3b7
Owner

But this is still part of the content. Wouldn't it be better to have some custom <meta> tag in the HTML <head> if this is only meant to check if the site is served at that domain?

But this is still part of the content. Wouldn't it be better to have some custom `<meta>` tag in the HTML `<head>` if this is only meant to check if the site is served at that domain?
Author
Owner

This way we can tell that the base template mechanism works.

This way we can tell that the base template mechanism works.
june approved these changes 2026-06-17 17:42:43 +02:00
june left a comment

Think this should work nicely. If @jtbx is happy with it, let's merge it.

Think this should work nicely. If @jtbx is happy with it, let's merge it.
Owner

This way we can tell that the base template mechanism works.

OK. I thought we wanted to catch mis-configured DNS, reverse-proxy and nginx. Because this was the main thing that was discussed in the chat as the monitoring went unhappy.

I'm just surprised that a HTML comment is even going through Hugo and ending up in the HTML and a bit unsure how stable this output will be. I would rather count this as a side-effect and not an actual feature that comments are preserved because some output options (e.g. minified) will strip comments.

And having something in the Hugo templates/ theme will also make sure that Hugo ran and used some content. The current proposal doesn't make sure that "the right" content was generated (whatever that actually means since it can change).

> This way we can tell that the base template mechanism works. OK. I thought we wanted to catch mis-configured DNS, reverse-proxy and nginx. Because this was the main thing that was discussed in the chat as the monitoring went unhappy. I'm just surprised that a HTML comment is even going through Hugo and ending up in the HTML and a bit unsure how stable this output will be. I would rather count this as a side-effect and not an actual feature that comments are preserved because some output options (e.g. minified) will strip comments. And having something in the Hugo templates/ theme will also make sure that Hugo ran and used some content. The current proposal doesn't make sure that "the right" content was generated (whatever that actually means since it can change).
Merge branch 'main' into status-canary
Some checks failed
/ cleanup-staging (pull_request) Failing after 2m16s
/ build (pull_request) Failing after 2m31s
0ab77c3bbc
stb merged commit 5263f294db into main 2026-06-19 08:55:30 +02:00
stb deleted branch status-canary 2026-06-19 08:55:30 +02:00
stb referenced this pull request from a commit 2026-06-19 08:55:31 +02:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
CCCHH/ccchh-website!170
No description provided.