pull down to refresh
50 sats \ 6 replies \ @optimism 19h \ parent \ on: OpenSats canary is out of date bitcoin
Funny how we have functionally the same solution.
I've gone off it in the past, and had some times of vacuum between solutions before it was a thing. However all my software uses prometheus for monitoring and I don't write anything without finegrained telemetry anymore, so I just have a stable environment for this now.
reply
reply
Ah, haha
You even also print ASCII art, I also do that if
figlet is installed:#!/usr/bin/env bash
...
command -v figlet > /dev/null
if [ $? -eq 0 ]; then
figlet -f graffiti bark 2> /dev/null && echo -e " your network watchdog\n"
fi
...
lol, leaked my ntfy channel id for a second, but wouldn't be a problem, since I could just create a new one
reply
reply
Btw, I’d love to open source my script, since I think it’s pretty cool (it even has a cool name:
bark), but it has a bunch of my IP addresses in there, and it reveals quite a lot about how I configured my network, and I don’t necessarily want to expose all of that to the public, or make it very configurable so I don’t have to hardcode all my private stuff, hahaHave you ever find yourself in a similar position?
#firstworldproblems
reply
Have you ever find yourself in a similar position?
I used to. However... at several points I had so much stuff running (I think my worst was 60+ servers and hundreds of containers both of the k8s and the lxc kind) that I just spent a month or so on migrating every script I had to take either env, or config files. Nothing hardcoded except maybe listening ports (since I anyway dockerize everything as microservices on k8s, this is not really a problem)
My biggest problem is figuring out whether code is mine or that I wrote it for one of my companies. Most often there's a
(c) statement in the header but not always.I'm pro sharing, but against dumping. I just try to share code sometimes in conversations.
reply