Self-Hosting Stories: Learn Self-Hosting Through Small, Real-World Tales - சிறுகதைகள் தொகுப்பு

I’m starting a series of self-hosting stories, where each tool is explained through a small story instead of a dry setup guide.

Self-Hosting Stories #1: The Little Bell That Rang (ntfy)

Story 1 is about Meera, who runs a home server. Her nightly backup script failed for 41 days and she didn’t find out until she needed a photo. The fix was ntfy, a tiny self-hosted service that sends push notifications to your phone from a plain HTTP request.

The story covers

  • The basics: topics, publishers and subscribers, using just curl
  • Self-hosting ntfy with Docker Compose and a reverse proxy
  • Locking it down with users, roles, access control and tokens
  • Making alerts useful with priorities, tags, click actions, attachments, delayed messages and action buttons
  • Subscribing from the mobile apps, the web, the CLI, or JSON/SSE/WebSocket streams

Read it here: The Little Bell That Rang — ntfy · Self-Hosting Stories

கதைகள் தொடரும் …

1 Like

Self-Hosting Stories #2: The Traffic Cone That Plays Everything

Ravi’s cousin’s wedding video won’t open on any device he owns, the files are old, one is half-copied, and the audio runs two seconds ahead of the picture. His friend Nisha has one answer: VLC.

In this story you’ll see how VLC repairs broken AVI files, fixes out of sync audio, converts old formats, records your screen, and streams video across the house. You’ll also find network radio and podcasts, remote control from a phone, and a keyboard shortcut cheat sheet at the end.

Free, open source, no ads, no account. Read it here: The Traffic Cone That Plays Everything — VLC · Self-Hosting Stories

கதைகள் தொடரும் …

Self-Hosting Stories #3: The Doorman Who Fetches His Own Keys

Karthik runs four small services from a rented VPS: a notes app, a photo gallery, a cricket-club wiki and a notification server. One Monday the club captain messages him about a scary red warning on the wiki. The certificate expired because his Certbot cron job had been failing silently for weeks.

This chapter follows how he stops renewing certificates by hand. He puts Caddy, a web server and reverse proxy that gets and renews HTTPS certificates by itself, in front of everything. A working site takes three lines of config.

It also covers the eMudhra incident, when browsers blocked that certificate authority’s keys and it announced its exit from the TLS business. Karthik’s cricket-club billing site was on a paid certificate from that CA, so the story shows why replacing a certificate has to be cheap and automatic. In Caddy, switching authority is a one-line change.

Read it here: The Doorman Who Fetches His Own Keys — Caddy · Self-Hosting Stories

கதைகள் தொடரும் …

Self-Hosting Stories #6: The Post Office in a Single Binary

GoDisai’s weekly newsletter grew from 9,000 readers in January to 84,000 by October. On the first of November, Meena opened the invoice and found the bill had nearly doubled. Crossing 75,000 readers had pushed the plan into the next tier, and she hadn’t sent a single extra email. On top of that, every learner’s name, city and course progress was sitting in a newsletter company’s database in another country.

This chapter follows how the team moves everything to listmonk, a mailing list manager written by Zerodha’s CTO to send a stockbroker’s contract notes and newsletters. It runs as one Go binary with PostgreSQL as its only dependency. It covers setting up SPF, DKIM and DMARC, importing 84,000 readers with only the opted-in ones, and segmenting them with a plain SQL query. It also shows how bounces are handled automatically and how class reminders and receipts go out through the same tool.

The cost is now based on emails sent, not on how many people subscribe. The learners’ data stays on your own server.

Read it here: The Post Office in a Single Binary — listmonk · Self-Hosting Stories 6

கதைகள் தொடரும் …

Self-Hosting Stories #7: The Whiteboard That Lives in Your Browser

Ayisha’s software studio in Coimbatore was building an appointment and prescription system for a group of eye clinics. The database design lived in three places that didn’t agree. One was a whiteboard photo pinned in WhatsApp that showed eleven tables when the real database had nineteen. Another was an online diagram tool whose free plan was about to drop to one diagram. The third was the migrations folder. Then the clinics IT head sent a vendor questionnaire, and Ayisha realised the full patient schema was sitting on someone else’s server under her personal account.

This chapter follows how Iqra, the studio’s database person, self-hosts drawDB. It’s an open-source database diagram editor that runs entirely in the browser, with no backend, no accounts and nothing stored on the server. The chapter covers building it from a pinned commit, serving it behind Caddy with a password, removing the analytics and running it under a subpath. It shows how to draw a diagram from a real pg_dump, design a new referrals table on the canvas, and turn the SQL export into a migration you still review line by line. It also covers the afternoon Ayisha cleared her browser data and lost two days of notes. After that, the team made a rule that the diagram file lives in git next to the migrations.

The schema stays on the team’s own machines, and the diagram finally matches the database.

Read it here: The Whiteboard That Lives in Your Browser — drawDB · Self-Hosting Stories

கதைகள் தொடரும் …

Self-Hosting Stories #8: The Family Album That Came Home

Yazhini’s family had a photo crisis: her Google storage was full, her husband’s was at 96%, and her father lost irreplaceable family photos when his phone fell into a water bucket. They were paying for cloud storage, yet the memories that mattered most were either lost or scattered across blurry WhatsApp groups.

This chapter follows how Yazhini selfhosts Immich, an open-source photo manager that works just like the big cloud apps but runs on a used mini PC at home. It covers setting it up using Docker, splitting the storage between a fast SSD for the database and a 4TB drive for uploads, and keeping facial recognition completely local so her family wouldn’t have to learn a new interface.

It also covers the golden rule of self-hosting: Immich holds your photos, but it is not a backup. It explores setting up that crucial second copy before deleting anything from Google, ensuring the family’s album finally comes home safely.

Read it here: The Family Album That Came Home — Immich · Self-Hosting Stories
கதைகள் தொடரும் …

Self-Hosting Stories #9: The Pendrive That Never Came Back

Karthik had one night before a hackathon demo and a 1.2 GB video to send to his teammate, who was sitting two benches away. WhatsApp compressed it, email rejected it, the pendrive set off an antivirus warning, and the cloud drive stalled. godisai.in

This chapter shows how LocalSend solves it. It is a free, open-source app that needs no internet, no account and no cloud. The file crossed the bench in under a minute. The chapter also covers how to stay safe when you use it in crowded rooms. godisai.in

Read it here: The Pendrive That Never Came Back — LocalSend · Self-Hosting Stories

கதைகள் தொடரும் …

Self-Hosting Stories #10: The Television That Would Not Stop Shouting

It starts with a 40-second soap ad that can’t be skipped, playing again and again in the middle of a TV serial. A family in Madurai had ads on everything: the smart TV, a speaker, and a tablet game, and none of these can run a browser ad blocker. godisai.in

This chapter shows how Pi-hole fixes this. It runs on one small, always-on machine and blocks ads and trackers for every device in the home. The chapter also covers when blocklists go too far and what to do when the power goes out. godisai.in

Read it here: The Television That Would Not Stop Shouting — Pi-hole · Self-Hosting Stories

கதைகள் தொடரும் …