Counterpoint: If you think you said something stupid, you’re entitled to delete it. Don’t feel obligated to hang your ass out there and take a beating for a cold take.
CTRL+Z
Counterpoint: If you think you said something stupid, you’re entitled to delete it. Don’t feel obligated to hang your ass out there and take a beating for a cold take.
Gotify. Home Assistant. DDClient.
This can be made even simpler by installing all the repos you want to mirror as submodules of the parent directory’s git repository. Instead of many git pull
or git fetch
, you blast a single git submodule update --recursive --remote
and go about your day.
Bonus: This has the added benefit of generating a git history for your automated process if you script in a commit message with a timestamp, making your mirrors reversible.
I think it’s bad to invent new words for “stopped container”
You’re not wrong!
Orphans are just dangling objects, are they not?
I’m only using the Unraid Docker GUI to send me utilization alerts and notify me when my images are egregiously out of date. I saw someone trying to author a compose file using the GUI once and I closed the window before the headache started.
I’m not paying $3/mo. Where’d you get that idea? I think I paid $20 for a license like 6 years ago.
I picked Unraid because I had a bunch of disparate HDDs sitting around and their filesystem intrigued me. (0 data loss after 3 drive failures so far.)
running out of disk space
This would be my first guess. Nothing shuts down arbitrary services quite like a full /var/logs
.
I’m running an Unraid server. You can pop in and manage everything with the CLI like you would on traditional server OSes and it’ll show your containers, images, orphans etc. in the GUI and throws alerts out of the box for utilization thresholds and power events. It’s quite nice at a glance and gets the fuck out of the way the moment it’s time to be a sysadmin.
Unraid brings some good things to the table, I wouldn’t discount it completely.
I have a Raspberry Pi 4B as my load bearing Mac mini.
Use containers. Start with one device. Check your utilization after you’re sure you’ve hit min and max for each of your services, then figure out if your single device can handle all your services gunning at once. If not, take your biggest service and migrate it to its own device.
Eventually, you might find yourself googling “Kubernetes vs Docker Swarm.” When you do that, take a deep breath and decide if upgrading one device is easier than trying to horizontally scale many.
Edit: Words bad. Verbs hard.
An UPS is a must for any computer, even if all it’s doing is absorbing the shock of a brownout and triggering a graceful shutdown.
I run persistent services that require 24/7 uptime.
Romm might fit, if you’ve got the patience to map controllers. Remember, it’s a BYO rom situation, but that’s nothing the guys over at @[email protected] can’t help you with.
If I have a closet with two Raspberry Pis running Docker Swarm, it’s a Private Cloud.
Fucking hell. Teach me more money spells, wizard.
(I already know about Scotty Time, framing sexy upgrades as “tech debt reduction,” and fending off trendy frameworks as “lacking maturity.”)
… according to a work trend index published Wednesday by Microsoft
Yeah, I’m going to go out on a limb here and call bullshit. No one is turning to AI to alleviate burnout. The only tasks these LLM tools can reliability accomplish aren’t worth using an LLM for.
Because fuck Lars Ulrich.
Did you use Shoelace, or is the name a coincidence?
“No.”
User requests come through ombi and I’ll reject whichever ones I feel like. No explanations, I just don’t.
Shout out to my fellow “None Backup Strategies” chaos goblins.