Wow, this is such a fantastic post. I love the visualisations!

This is great, I've needed something like this quite a few times. I always end up just stumbling my way through how to modify an SVG.

Truly a great post. Not a video, just a straightforward building blocks approach to teaching a concept- the examples really make it shine.

Finally it works as it should I update my old nginx version to newest freenginx and read Thoroughly the location documentation and this post thanks to @ramble81@lemmy.zip

Thank you @ramble81@lemmy.zip 👍
Post saved !

I ran into something similar and the docs didn’t make sense. This link helped figure things out.

You might have another location block before it that catches the route.

Actually I don't think the error lay in the regex.

because

	location /fileA.txt {
		return 404 'nothing here';
	}

Does not works either...

Thanks @elbucho@lemmy.world

I've tried

	location ~* \/(fileA\.txt|fileB\.md)$ {
		return 404 'nothing here';
	}

but still not matching :'(

Apparently ngx_http_rewrite_module "module" is installedby default with nginx... damn thay should use diffrent terms for what could be install or not at compile time..

You aren't escaping your periods. Try like this:

location ~* \/(fileA|fileB)\.txt$ {
        return 404 'nothing here';
}

Never mind, I understood my mistake... This nginx built didn't come with ngx_http_rewrite_module so return will not works.

Derek Sivers has a very simple and direct implementation for static comments.

Oh I like that! Thanks for the idea.

It was usefull for me. Not everyone is a webdev 🙂

Both root and www. seem to work. Thanks for the switch!

Exactly what I needed !

I recently moved my blog from wordpress to markdown based using pelican and codeberg and I was looking for hosting solution.

I just managed to deploy it to statichost (https://kissyagni-blog.statichost.eu/). I struggled a bit with DNS redirection but it seems to work now. Can anyone confirm ? https://kissyagni.com/

If you want to make your site more interactive but not necessarily with comments, look at the Open Heart protocol.

It’s a cool implementation where people can literally hit like on your writings whether they’re reading your site in the browser or within their RSS feed readers.

https://openheart.fyi/

There's ways to integrate Mastodon comments, if that's up your alley. I don't know the technical details, but basically a Mastodon post linking to your blog post would show up on the Fediverse and when people respond to that post using the "public" privacy setting, then that post will show up on your website.

If you tagged a Lemmy community in that Mastodon post, it should also federate over here, although I'm not sure, if responses will also show up.

Unsurprisingly, there's a gazillion blog posts out there on how to set this up, but here's just a couple:

• https://berglyd.net/blog/2023/03/mastodon-comments/
• https://andreas.scherbaum.la/post/2024-05-23_client-side-comments-with-mastodon-on-a-static-hugo-website/
• https://lauralisscott.com/blog/mastodon-comments-hugo-static-site/

And of course, if you scroll down to the bottom of those pages, you can see how the integration looks like.

From what I've seen when quickly scanning the posts, I believe, they're using different plugins to do this. The first link I posted discusses a plugin developed by Carl Schwan, who's also a KDE dev and he's here on Lemmy, too, so that would be what I'd personally try, without knowing anything else about these plugins. 🙃

If you want to keep it fedi related there are apparently ways to implement mastodon as comments

There's always Disqus. But here are a few more alternatives:

• https://cactus.chat/
• https://cusdis.com/
• https://chirpy.dev/
• https://convocomet.dev/

If you move to free hosting on github pages, you could also use Github discussions: https://github.com/features/discussions

Which is not very noteworthy, don't you think?

Putting some HTML files on a web server somewhere is not that big of a mystery in 2025 that it might have been in 1995.

Github Pages supports Jekyll as a SSG out of the box.
Any documentation or tutorial – official or otherwise – that simply skips on this is getting people’s hopes up just to waste their time.

Yes, but this is about parting from GitHub and using Codeberg + statichost.eu instead, which does not do everything automatically.

Github Pages supports Jekyll as a SSG out of the box.

Any documentation or tutorial – official or otherwise – that simply skips on this is getting people's hopes up just to waste their time.

Nice, thank you ✌️ just wanted to avoid getting into a nightmare!