Yes. I literally had to close a bank account to get Planet Fitness to stop charging me.

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

I wonder what the aim is. Trying to get relevant again? I haven’t used Winamp in many many years. I’m a Spotify / YouTube kind of guy now. I drank the koolaid. It’s a little late and things like VLC have a pretty solid offering now, without all gotchas that this will have (such as you apparently can’t call it Winamp and will have to sign away a sacrificial child to actually get the code)

I like my Kubernetes setup at work. It runs Nextcloud, Mattermost, GitLab, company website, several embedded firmware OTA update sites, a few internal apps. Nextcloud was pretty easy to install on it with Helm, just a single command line and a yaml file to specify domain, settings, etc. I had some teething issues in my early setup where the database would get wiped inexplicably, but it’s been running smooth for years now. (Yes, I know, bad juju running databases on Kubernetes…I’m used to it and it mostly works)

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.

I’m not so sure. I seem to be able to find my way around a GitLab project in much fewer moves than a GitHub project. But maybe I’m biased because I use it all the time at work. I know they change the sidebar a lot, though.

I had to close my bank account to cancel mine. I moved and didn’t want to head all the way back to go in person to cancel. They wouldn’t accept a cancel request online or over the phone. Why is it always gym memberships that want to be next to impossible to cancel?

Proud GitLab self-hoster here (for private projects). I’d love for someone to beat GitHub. The hard part is going to be replacing the discoverability and the network effect. I find GitLab to be a superior product, technically, but it doesn’t matter much in the face of GitHub’s momentum as the incumbent 800 lb gorilla.

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.

At first, because Microsoft bribed me with reward points for using it. Then I came to realize Bing wasn’t all that bad. Until about a year ago when they started pushing the chat stuff.

It took me a lot of practice. I used to get mad at everything too. Almost violently so (hence the username “fury”). I realized over time I don’t want to spend that much effort being mad at anything. It’s not worth it. I’m going grey fast enough as it is without willingly adding to it. I’d rather focus my energy on something more enjoyable.

Except Bing Chat. Bing Chat can go take a long walk off a short pier, and I wish everybody who worked on Bing Chat a very “good heavens what were you thinking”. Give me back my regular search results, thank you very much.

Even worse is taking over the back button / back gesture to redirect you to “more to read before you go”

Me still trying to figure out how to get it to auto start / auto login on boot on my fresh new Raspberry Pi 5 without locking up at a flashing cursor screen: 😩

Good luck getting all the developers to rewrite their apps. The only reason you had any apps was because it was based on Android so it was little to no effort to port. Going plain ol’ embedded Linux is basically the death knell of your developer story. Source: been there, had no third party apps, switched to Android

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.

I just want a picture of a goddang hotdog

Take a look at hosting your own Nextcloud instance. It’ll replace Google drive, photos, docs, everything–there’s phone apps for iPhone and android. If you want to store your PC backups on it, that’s probably fine too. It might even work ok on the Pi 4 (though some parts it has integrations with may have trouble, like Nextcloud Office, since they may not have ARM binaries in their distribution).

It should work great on your local network and still be acceptable when uploading out and about (photos can auto sync if you turn that on on your Nextcloud phone app).

If 4TB is enough for your needs, I’d suggest getting another 4TB and making them a RAID1 pair using mdadm, and then probably also another 4TB to make backups of Nextcloud and Nextcloud data onto to keep offsite. You can never have too many copies of your data.

I’m not sure what to do about the variety of smaller drives. I can say I wouldn’t recommend consolidating them onto a single drive, because I did that once (many drives ranging from 60 gigglebytes to 300, onto one 1.5 TB drive) and then formatted or got rid of the smaller ones…and then dropped the 1.5 TB drive on the floor while it was running. Rip. But just like the above, a RAID1 array composed of two big drives would probably be fine.

Just make sure to set up some alerts for when a drive fails.

When you decide

fury get mad sometimes