Last week, I published a post about my experience at a startup weekend competition—our team won, and I wanted to share the lessons. On April 23rd, I submitted the link to Hacker News. The next morning, I woke up to a surprise: Umami showed a 5,000% increase in visitors over the past 24 hours. Hacker News 5,000% increase Normally, my blog gets 50–100 daily views. But in just 4 hours, I had nearly 1,300. According to the Wayback Machine, the article peaked at #16 on Hacker News—something I’d never even dreamed of. Wayback Machine #16 on Hacker News By the end of the day, my site had served 194,000 requests—and it never went down. 194,000 requests And yes… I even started a Docker build on the same server during the spike before reviewing the analytics. Was I Ready for That Much Traffic? No. At least, not intentionally. But thanks to past experimentation with caching and web performance optimization, my setup handled it. I use Ghost CMS for my blog, and last year I invested time in tuning it for performance. caching web performance optimization Ghost CMS How I Prepared: Two Layers of Caching 💡 The key to surviving unexpected spikes is caching—especially layered caching. Here's what worked for me: caching 1. Cloudflare in Front My blog isn’t directly exposed to the internet—it’s behind a Cloudflare proxy. This helps: Cloudflare proxy Block malicious trafficProvide a global CDN for caching static assetsReduce server load by serving cached responses from edge nodes Block malicious traffic Provide a global CDN for caching static assets Reduce server load by serving cached responses from edge nodes 2. Cache-Friendly Ghost CMS Configuration I also fine-tuned Ghost’s cache headers to help Cloudflare do its job. Here’s what I set in my Docker Compose .env file: .env caching__contentApi__maxAge=60
caching__frontend__maxAge=60
caching__robotstxt__maxAge=36000 caching__contentApi__maxAge=60
caching__frontend__maxAge=60
caching__robotstxt__maxAge=36000 This tells Ghost to set proper Cache-Control headers, so responses are cached both in browsers and by Cloudflare—especially useful when hundreds of users hit the same page simultaneously. Cache-Control 🔗 Learn more in the official Ghost documentation official Ghost documentation How Cloudflare Saved My Server Cloudflare was critical. Here’s how I set it up: Admin portal excluded from caching (for security and accuracy)Everything else set to “cache everything” with respect to origin headers Admin portal excluded from caching (for security and accuracy) Admin portal excluded Everything else set to “cache everything” with respect to origin headers Everything else As a result, 94% of all requests were served from cache during the Hacker News spike, according to Cloudflare Analytics. 94% of all requests were served from cache This drastically reduced the number of requests reaching my actual server and you can see that in the following graph. Cloudflare cached up to 94% of all traffic going to danielpetrica.com My Stack: Minimal, Scalable, Docker-Based My infrastructure uses: Docker Compose + Traefik for reverse proxying. read more here.Cloudflare for security and caching.Ghost CMS for blogging~24 self-hosted sites and tools (like Activepieces ) on a single 4 core ARM server. Docker Compose + Traefik for reverse proxying. read more here. Docker Compose Traefik here Cloudflare for security and caching. Cloudflare Ghost CMS for blogging Ghost CMS ~24 self-hosted sites and tools (like Activepieces ) on a single 4 core ARM server. Activepieces Even while building a Docker image during the spike, the system stayed fast and responsive. TL;DR: Want Your Blog to Survive Hacker News? Here’s what worked for me: Put Cloudflare in front of your siteConfigure your CMS to set cache headers correctlyUse Docker + Traefik for modular, scalable hostingAvoid overcomplicated setups—opt for stability and cacheability Put Cloudflare in front of your site Configure your CMS to set cache headers correctly Use Docker + Traefik for modular, scalable hosting Avoid overcomplicated setups—opt for stability and cacheability Need Help Setting This Up? I’m a freelance DevOps and monitoring consultant, and I can help configure your Ghost (or other) stack for performance, caching, and observability. DevOps and monitoring consultant Mail me or visit click the button bellow if you'd like help prepping your server for a Hacker News-level spike. Contact me via mail to discuss how I can help you. Write an email to me Write an email to me Thanks for reading this far! I’ll definitely share more about my stack, my experience as a startup founder, and programming tips in future posts. If that sounds interesting, feel free to subscribe—it's free, and you'll be the first to know when new content drops.

How I Kept My Server Alive Through the Hacker News Front Page Rush

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

An AI-Powered Workflow Automation Guide: How You Can Self-Host n8n with Docker Compose and Traefik

An AI-Powered Workflow Automation Guide: How You Can Self-Host n8n with Docker Compose and Traefik

Light-Mode

Classic

Newspaper

Minty

Dark-Mode

Neon Noir

Minty

HN StartUps