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.

No more biting down on my tongue or cheeks when eating. Most annoying glitch ever.

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.

https://everynoise.com

Every music genre you can think of, and then some. I finally found out what the stuff I like is called.

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

Dihydrogen monoxide. That stuff’ll kill you.

I get mad sometimes

It’s lighter than a VM but a bit heavier than aiming to run an application natively (and all the dependency & configuration hell that entails).

Basically a convenient way to package and run applications with all their dependencies, without regard for what libraries & configurations exist in the host OS and other containers.

If your application only works with up to version 42 of the Whatchamacallit library, you ship it with that version of Whatchamacallit, the underlying OS doesn’t need to install it. Other containers running on the system that depend on that library don’t get broken since they’re packaged with version 69 which works fine for them.

Meme answer:

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

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.

I always google on Bing.