Recent submissions

Comment · 2 years ago
This tool lets you explore how Varnish reacts to HTTP cache headers. I created it to help myself and others learn about HTTP caching semantics.

You can run it locally against a Docker-based Varnish instance, or try out some predefined examples (with hard-coded responses) on the demo website.

Comment · 4 years ago
Interesting, I hadn't considered that -- thanks. I was just having a look and it seems that right now, only Chrome and Edge (and Brave?) support that API. I'll keep an eye on it, because it doesn't seem like a viable option yet until Safari and Firefox also do.
Comment · 4 years ago
Thanks, I had been looking for existing glossaries with permissive licenses to use as examples, and this one wasn't on my list yet. It does look way larger than any of the other examples. But it would be interesting to explore what sort of changes would be required to the template to keep it usable in practice.
Comment · 4 years ago
Yes -- you beat me to it :-).

The built-in server is meant to be run only locally/offline (typically by a developer), just for making changes to a glossary. If you download and open the template (not one of the "full" examples) in a browser, then it tells you how:

sed -n '/START OF editor.js$/,$p' glossary.html | FILE=glossary.html node

Then you would host glossary.html (and maybe the CSS and JS if you don't want to point to the CDN) wherever you want, as it's just a static web page.

I will make this clearer in the documentation -- thanks!

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton