Skip to content

Nguyễn Minh Hiếu

@homelab_hieu

Proxmox, Docker, ZFS, and a power bill my wife asks about. HCMC 🇻🇳 Backend dev by day, homelab by night. Founder of Self Hosted. Back up your data, seriously.

  • Ho Chi Minh City, Vietnam
  • Vietnamese · English
  • Joined May 2026
  • Last posted Oct 8, 2026
Posts
9
Followers
39
Following
15
Reputation
538

Posts

Everything this author has published.

12

  • the bare "media/" exclude is a classic. i did the same thing with "cache" in 2014 and excluded a directory called cache that held a client's entire product image library. found out when they asked for a restore. aye. three more for the list: 1. 3-2-1. three copies, two kinds of media, one offsite. B2 is your offsite, the NAS is copy one, get a cheap usb disk for copy two and rotate it 2. one copy should be something ransomware cannot delete. B2 has object lock, use it, or at least an app key that can't delete 3. write the restore steps down. on paper. the person restoring might be your wife, and she won't have your bash history
    1 reply
  • pg_dump. Always. A filesystem copy of a running database is not a backup.
40 votes · Ended
10

  • port forward + reverse proxy + fail2ban since 2009. never been pwned. that i know of
    1 reply
  • WireGuard. Ten lines of config. Done.

  • And check for data. If it had Portainer open, assume whatever was in those containers is gone. If any of it is other people's personal data, that is a breach, not a bad day.
8

  • Good post. One privacy nuance people should understand: recursive resolution is better than handing everything to Google, but the queries to the authoritative servers still go out unencrypted, so your ISP can still see them. Forwarding over DoT to a provider hides them from the ISP but then you trust that provider. Neither is "private". Pick your adversary.
    1 reply

Best answers

Get the best of Dynamo Geeks weekly

One email each Monday with the most useful posts. No spam; unsubscribe in one click.