tool

Edit: on the other hand, does the latest nginx get pulled at time of creation?

It depends on how you have your docker compose file set up. If you pin the version, no, it’s never going to get updated unless a new version with that exact tag is released. If you omit the tag, it’s going to default to whatever is tagged as latest in the image repository, and that’s only going to actually update the image when you either manually pull the image or relaunch the compose stack.

If you want it to auto-update without relaunching the stack or manually pulling the latest image, you’d have to set up something like Watchtower and have it monitor that container.

That certainly makes me feel better for letting the Magic Smoke out.

I don’t think it became easier at all until it was forked off into Xorg and they started making dramatic improvements.

I think it was trial and error for hours at least.

It certainly was until I discovered the monitor I hadn’t fried had the modelines printed on a sticker on the back…

So I’m not the only one who fried a monitor trying to get X11 working…

and how hard it was to get x11 working

Oh good God. If you really want to test someone’s resolve, sit them down at an old computer with a CRT and no Internet and have them configure X11 from scratch. Seeing that default X11 crosshatch background for the first time was practically orgasmic after the bullshit I went through to make it work.

That’s one of those traumatizing experiences I’d completely blocked from my memory until I read your comment.

Traumatizing experience #2 that just came back to me was getting a winmodem working and connected to my ISP via minicom.

Just added it to the massive Google graveyard next to Stadia, wave, hangouts, plus, music, etc etc

I am shocked and appalled that Google Reader didn’t get called out in this list and is relegated to the “etc” category.

It deserves more than “etc.”

Gotcha. I’m actually in the process of moving away from Namecheap because of an experience I just had with them. I tried to register a domain about a month ago (the domain my Lemmy instance is on) and it stopped the registration process immediately after I hit the Pay/Checkout/whatever button and told me to contact their support team to register it.

The error message said it was because the domain name was too similar to something that already existed, and that the support team would have to decide whether I’d be allowed to register it or not. So I went to another registrar and registered it with no issue. I really didn’t like that, and it’s enough to make them lose me as a decade+ long customer. I already use Route53 for DNS for all my domains, so it’s not like I was using them for anything else other than a registrar, so untangling that shouldn’t be too much of a pain.

It only costs $6 a month plus the $35/yr for the domain name

My man, you are getting absolutely bent over a barrel by your registrar. You could get that domain significantly cheaper at a place like Porkbun or Namecheap.

just raise awareness about tools like this one https://lemmyverse.net/

I also think that something like LCS or Lemmony should be recommended and/or included in the default Lemmy docker compose file.

That way, when new Lemmy servers get spun up, they will automatically get seeded with content and communities from other existing Lemmy servers.

At work/for business, you can’t beat Veeam. It’s the gold standard and there is literally nothing better.

At home, Duplicity. Set it up once and then just let it go, and it supports a million different backup targets you can ship your backups off to, including the local filesystem. Has auto-aging/removal rules, easy restores, incrementals, etc. Encrypts by default too.

I still haven’t found a replacement for it.

Oh man, this takes me back…

It’s a decade later, and I’m still bitter about Google Reader’s unceremonious execution.

If it’s that old, I’m betting it doesn’t use HTTPS for its connections. You could do a network packet capture on the XP machine (or if you can find one, hook it up to a network hub with another computer attached and capture there) while performing the “clear error” action and find out how it works/what you need to send to it to clear the error. You could also set up a SPAN port on a switch and mirror the traffic on the port going to the printer to capture the traffic, if you have a switch capable of doing that. If not, you can get one off Amazon for about $100.

It’d be pretty simple to put together a script that sends the “clear error” action to the printer after seeing how it’s done in the packet capture. I’ve done this numerous times, the latest of which was for a network-connected temperature sensor that I wanted to tie into but didn’t (publicly) expose an API of any kind.

Throw in a mysterious comment that says “Don’t change anything below this line or everything breaks” and it’s complete.

“We don’t know why this works, but it does, don’t touch it.” would also be acceptable.

Some places are insanely polluted to the point where you wonder how a whole company could be so braindead and essentially poison themselves.

“That’s the future guy’s problem, my problem is making money.”

No need to wonder. That’s how.

Unless you’re really deep into a particular provider’s unique-esque products (Lambda, Azure AD, Fargate, etc), this is exactly why things like Terraform exist.

Places like that never learn their lesson until The Event™ happens. At my last place, The Event™ was a derecho that knocked out power for a few days, and then when it came back on, the SAN was all kinds of fucked. On top of that, we didn’t have backups for everything because they didn’t want to pay for more storage. They were losing like $100K+ every hour they were down.

The speed at which they approved all-new hardware inside a colocation facility after The Event™ was absolutely hilarious, I’d never seen anything approved that quickly.

Trust me, they’re going to keep putting it off until you have your own version of The Event™, and they’ll deny that they ever disregarded the risk of it happening in the first place, even though you have years’ worth of emails saying “If we don’t do X, Y will occur.” And when when Y occurs, they’ll scream “Oh my God, Y has occurred, no one could have ever foreseen this!”

It’ll happen. Wait and watch.

You’re literally describing the system that controlled employee keyscan badges a couple of jobs ago…

That thing was fun to try and tie into the user disable/termination script that I wrote. I ended up having to just manipulate its DB tables manually in the script instead of going through an API that the software exposed, because it didn’t do that. Figuring out their fucked-up DB schema was an adventure on its own too.

I don’t even let things communicate on /30 networks via HTTP/cleartext…this whole thing is horrifying.