Work in progress: 181,232 of 181,233 sites checked so far, more every week · updated 2 Nov 2026Missing a blog? Tell us

Top all-time · #13639

F

Florin Lipan

Personal blog · lipanski.com/posts · on HN as lipanskiprogrammingsystemsweb

Florin Lipan's personal blog at lipanski.com covers programming, systems and web. Since 2020, 5 different Hacker News readers have linked it 9 times, most often “A tiny Docker image to serve static websites”. The last post was in 2021, but the archive is still widely read.

Visit the blog
9mentions?
5HN people?
2020–2024first – last linked?
Links on Hacker News per year · peak 4 in 2020

Too few sampled comments (1) to say how often HN recommends it.?

Why HN links it

HN readers link this post about building a very small Docker image for a static web server, about 154KB. One commenter cites it as a source for how small web servers can be.

Summarised by Claude from a sample of 1 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.

My personal website

The author on HN?

lipanski · 291 karma · member since 2013

https://lipanski.com

From their public HN profile, which links to this site.

Most-linked posts?

  1. A tiny Docker image to serve static websites
    4 people · 4 mentions · first linked 2021-03-01
  2. Speed up your Docker builds with –cache-from
    2 people · 2 mentions · first linked 2020-04-27

What Hacker News says?

  1. One of the most common mistakes I see is not using a .dockerignore file or, better said, relying on .gitignore when calling `COPY` on entire directories. Without a .dockerignore file in place, you could be copying over your local .env files and other unwanted things into the final image. On top of that, you might also want to add `.git/` to your .dockerignore file, as it could significantly reduce the size of your i…

    Comment linking /posts/dockerfile-ruby-best-practices

    on “Dockerfile Security Best Practices”
  2. Submitted A tiny Docker image to serve static websites as a story · 374 points

    HN discussion
  3. In my experience, automatic eager loading is the most elegant solution to this problem. For ActiveRecord, I'd recommend Goliloader [1] (which is a gem similar to ar_lazy_preload but with emphasis on doing that automatically) while for Sequel, you can enable the TacticalEagerLoading plugin [2]. These tools don't require explicit `includes`or `preload` calls. They can infer the tables that need to be eager loaded thro…

    Comment linking /posts/activerecord-eager-loading

    on “How to GraphQL with Ruby, Rails, Active Record, and No N+1”
  4. Submitted The smallest Docker image to serve static websites as a story · 3 points

    HN discussion
  5. Web servers aren't big! Browsers are huge but servers can be tiny. I'm sure Caddy and nginx and the like are at least 2MB, but they have a lot of features. Googling around a bit for small web servers, I found this fun blog post: https://lipanski.com/posts/smallest-docker-image-static-webs... They ended up with a static web server in a 154KB Docker image.

    Comment linking /posts/smallest-docker-image-static-website

    on “Webview: Tiny cross-platform webview library for C/C++”
  6. Submitted Some things you should know about eager loading in ActiveRecord as a story · 3 points

    HN discussion
  7. Submitted Speed up your Docker builds with –cache-from as a story · 2 points

    HN discussion
  8. Submitted Speed up your Docker builds with –cache-from as a story · 1 points

    HN discussion
  9. Submitted The smallest Docker image to serve static websites as a story · 1 points

    HN discussion

Search all of HN for lipanski.com