• 1 Post
  • 28 Comments
Joined 2 months ago
cake
Cake day: September 17th, 2026

help-circle
  • ultimaluz@lemmy.worldtoSelfhosted@lemmy.world•I went vpn only
    link
    fedilink
    English
    arrow-up
    2
    ·
    23 hours ago

    same here more or less, at home nothing is open anymore, everything goes through tailscale and a raspberry pi that also does the wake on lan for the big pc when I need it. the only thing exposed is a hetzner vps with a small browser game, and there I keep it boring, ufw with just 80 and 443 (and rtmp for a stream relay), caddy in front, the node app and postgres only reachable from inside the box. I guess that’s the trade off that works for me, whatever strangers need to reach lives on one machine I watch closely, the rest stays behind the vpn




  • not weekends but I had one that failed on two random days in a month and looked totally fine the rest. it’s a scheduled job that reads a couple of sites through a logged in browser on my laptop, and those two days the browser just wasn’t connected, so the job ran on time and had nothing to read. the log said “ok, nothing new” which is the worst kind of failure lol. now it uses a browser that keeps its own session and the other one only as fallback, and an empty result gets reported as a failure and not as a quiet day. same lesson as yours I guess, check what else has to be alive at that moment, not only what’s running


  • from the other side, i’m the cto of a small agency and i wrote our rules for working with ai, so maybe it helps. the first one is that the author answers for the code, “the model did it” is not an explanation for anyone. asking the model to review its own diff is a first pass, not a review, the same model that got it wrong is checking itself. the way i put it to the team, ai makes producing cheaper, not deciding or verifying, if you ship double with the same error rate you get double the errors. if your company only measures volume, the atrophy is more a management problem than yours, i’d push back with incidents and rework numbers, thats the language they listen to


  • i run a small browser game on a hetzner vps and for me the bots were never a load problem, it was the stats. the game shows how many people are online and every crawler that opened the live stream counted as a new player, in early october it was 28 of 61 stream opens. then a headless chromium on residential proxies, different ip every time, made 40 fake players in two days. what caught it was the Sec-CH-UA header, it said chromium 146 while the user agent said chrome 120, real browsers don’t mismatch like that. i don’t block them now, they just stop counting as people, which is kind of depressing too i guess


  • nice! for anyone with postgres in the mix, what bit me wasn’t the backup itself but the disk. a table in my side project kept one snapshot per minute and never deleted any, the disk hit 100% and postgres went down with a PANIC for like 40 min. now the nightly pg_dump writes to a .tmp, checks it with gzip -t and only then replaces the old file, and the app warns me if the newest dump is older than 26h or suspiciously small. restoring is just loading it into an empty db and starting the app, boring but it’s the part you actually want to know works





  • Plan sounds fine to me, debian + immich in docker + tailscale is pretty much the boring setup and boring is good for a box in a shed. one thing I’d do before carrying it out there, install tailscale and ssh, reboot it a couple of times and make sure it comes back on its own without a screen, because walking to the shed with a monitor gets old fast. also something like uptime kuma on another machine (or your NAS) pinging it, so you know it’s down before you’re on holiday and the photos stop uploading. I run a box at home I only reach over tailscale and that’s the part that saved me most.





  • on the fear part, in a healthy team the author still owns the change, the reviewer is a second pair of eyes not an insurance policy. what helped my people a lot was asking the author how they tested it and what happens if it goes wrong, if they can’t answer that’s your review comment right there. and if something breaks after you approved it, you fix it together and add a check so it doesn’t happen again, nobody serious blames the reviewer for that


  • They don’t go away on their own, every installed snap is mounted as its own loop device and snapd keeps an older revision or two so it can roll back, so the number moves around after updates. snap list --all shows which snaps they are, if one says disabled that’s the old revision and you can remove it with sudo snap remove <name> --revision=<rev>. about libation, if it’s installed as a snap itself that could be the actual problem, snaps are confined and can’t read folders outside your home or on other drives unless you connect the removable-media interface, so I’d check that before worrying about the loop devices.