Sharedrop

Open source. Works about as good as AirDrop when that isn’t available.

Regrets aplenty after some of the things I’ve drank, but none of them are about Debian.

My ringtone has been the same one for the last 15 years, Cowbell Rock. I paid for it twice, once when Ringtone Feeder was a thing, and then again from iTunes. Worth it. Best ringtone ever. Would buy again if I could.

A little slower by today’s standards, but if your needs are light, it’ll do the job. Keep in mind it only has a gigglebyte of RAM, so its capacity for running things may be limited, especially as docker applications go (since they bring a copy of each dependency). You won’t be able to run something as large as GitLab or Nextcloud, but a smattering of small apps should be within its capabilities

The thing with using the “latest” tag is you might get lucky and nothing bad happens (the apps are pretty stable, fault tolerant, and/or backward compatible), but you also might get unlucky and a container update does break something (think a 1.x going to 2.x one day). Without pinning the container to a specific version, you might have an outage suddenly due to that container becoming incompatible with one of your other applications. I’ve seen this happen a number of times. One example is a frontend (UI) container that updates to no longer be compatible with older versions of the backend and crashes as a result.

If all your apps are pretty much standalone and you trust them to update properly every time a new version of the container is downloaded, then you may never run into the problems that make people say “never use latest”. But just keep an eye out for something like that to happen at some point. You’ll save yourself some time if you have records of what versions are running when everything’s working, and take regular backups of all their data.

There are dozens of us! Maybe we should find or start a siren community on Lemmy. I just don’t have time to moderate, or I’d do it…

don’t dead open inside

The problem child for me right now is a game built in node.js that I’m trying to host/fix. It’s lagging at random with very little reason, crashing in new and interesting ways every day, and resisting almost all attempts at instrumentation & debugging. To the point most things in DevTools just lock it up full stop. And it’s not compatible with most APMs because most of the traffic occurs over websockets. (I had Datadog working, but all it was saying was most of the CPU time is being spent on garbage collection at the time things go wonky–couldn’t get it narrowed down, and I’ve tried many different GC settings that ultimately didn’t help)

I haven’t had any major problems with Nextcloud lately, despite the fragile way in which I’ve installed it at work (Nextcloud and MariaDB both in Kubernetes). It occasionally gets stuck in maintenance mode after an update, because I’m not giving it enough time to run the update and it restarts the container and I haven’t given enough thought to what it’d take to increase that time. That’s about it. Early on I did have a little trouble maintaining it because of some problems with the storage, or the database container deciding to start over and wipe the volume, but nothing my backups couldn’t handle.

I have a hell of a time getting the email to stay working, but that’s not necessarily a Nextcloud problem, that’s a Microsoft being weird about email problem (according to them it is time to let go of ancient apps that cannot handle oauth2–Nextcloud emailer doesn’t support this, same with several other applications we’re running, so we have to do some weird email proxy stuff)

I am not surprised to hear some of the stories in this thread, though. Nextcloud’s doing a lot of stuff. Lots of failure points.

I have an odd obsession with tornado sirens and other civil defense things. The odd harmonies that different kinds of sirens can make together. Cold War vibes, and the feeling of “well, we’re fucked then” when the emergency alert system goes off, only to find that it’s just another ho-hum thunderstorm on the other side of the city. I don’t know a whole lot about the stuff but I’ve spent many hours of many days soaking up videos about it on YouTube.

I miss when all school kids had to worry about was fire, tornado, earthquake, and nuclear annihilation.

I got talked into bankruptcy (by a bankruptcy lawyer, surprise surprise). It cleared $12k of credit cards and bank fees but not the then-$50k of student loans and the spending habits that were the real problem. Now I learned my lesson. No credit cards. Save up and pay. Have an emergency fund that can cover your expenses for months and months in the event you lose your job, or your most expensive unplanned repair. That’s the real life saver.

I had an 8 digit, lost the password, had to sign up again and got a 9 digit number that time. Felt weird.

How many digits?

I’m dying to know which letter it is.

Ah, yes, good old metric time.

Pressing F to pay respects. R.I.P. in pieces

Depending on how mission critical your data is…Set up delayed replicas and backups (and test that your backups can actually be restored from). Get a second pair of eyeballs on your query. Set up test environments and run it there before running it in production. The more automated testing you put into your pipeline, the better. Every edit should be committed and tested. (Kubernetes and GitLab Auto DevOps makes this kind of thing a cinch, every branch has a new test environment set up automatically)

Don’t beat yourself up too much though. It happens even to seasoned pros.

fury get mad sometimes

This is my little setup at work

Kubernetes cluster (created by kubespray)

• “Glue” services:
  • nginx ingress controller (automatically sets up nginx vhosts for Kubernetes apps)
  • cert-manager (gets SSL certificates from Let’s Encrypt for any apps that need them)
  • MetalLB (finds and provides an IP for Kubernetes services)
  • rook (storage provisioner–I have a few partitions & drives dedicated for rook to provide storage to the apps on the cluster)
• Apps:
  • GitLab (via GitLab helm chart which brings along nginx ingress and cert-manager)
  • Nextcloud (via Nextcloud helm chart)
  • Mattermost (via Mattermost helm chart)
  • Rancher
• Apps deployed via GitLab CI/CD (primarily through Auto DevOps):
  • Company website
  • Firmware updates for embedded systems
  • Mobile apps

BROWSERS!

Reminds me of when I had to change my site’s login cookies from “session” cookies to “persistent” cookies because mobile browsers aggressively clear the session. I don’t know if that’s what was going on in this case.