Hacker News Reader

Comment by astrea | Hacker News Reader

Guys: Serve your blog via Docker itself. Docker image names are _already_ URLs. You could literally just have people do `docker pull myblog.com/recipes:latest` or `myblog.com/recipes:lasagna`.

Edit: and navigate like so: `docker image myblog.com/recipes` to list all recipes. God I love APIs.

View on HN

And add search logic to the tag, so you don't need to know the name of the post, just the right word(s) to find it and let the "I'm feeling lucky" algorithm pick the right one :)

And then someone ports that back to regular Docker, and we get a whole new dimension of software supply chain security issues :).

I can't tell how much of this is sarcasm. Turning what started out as a problem of "How do you load arbitrary remote TROFF sources into man" into "throw docker at it" because someone suggested an intermediate solution of "apt" which introduces security issues and no one posed that there might be an alternative that obviates any need for containerization. I mean these two things could be further from each other on the scale of incredibly lightweight to massively heavyweight.

Or maybe this is a microcosm of why docker and kuberwhatever happens so much.

It's the nerd version of that Reddit pattern of organic comment chain, each reply adding e.g. a line of song - only with pushing an absurd idea to the limits.

I'll bite: with GP's take, docker-compose would make for a good webring/blogroll. Or use it as bookmarking system.

  cd blogs/cooking
  docker-compose up
  # 20 different recipe blogs available as man pages

Exactly this. Just having fun.

I can confirm that I was jesting when I said to use Docker here :^)

I thought we were just riffing, I wasn’t actually proposing this as a genuine technical solution. Just a fun thought experiment :)

It's probably more satire than anything else.

Weekend project: Docker pull blog posts over DNS

Reply on news.ycombinator.com