That particular one is long gone I’m afraid, but it’s essentially just docker compose down, tar like I did above, docker compose up -d, and then I used rclone to upload it

Seconded, and great callout @RadDevon@lemmy.zip , yes part of my script was to stop the container gracefully, tar it, start it again, and then copy the tar somewhere. it “should” be fine, in a production environment where you could have zero downtime I would take a different approach, but we’re selfhosters. Just schedule it for 2am or something.

Oh, and feel free to test! Docker makes it super easy. Just extract the tar somewhere else on the drive, point your container to the new volume, see if it spins up. Then you’ll know your backup strategy is working!

If you’re using docker (like your DBs run in docker), then I think you’re overthinking it personally. Just back up the volume that the container uses, then you can just plop it back and it will carry on carefree.

I usually did a simple tar cvf /path/to/compressed.tar.gz /my/docker/volume for each of my volumes, then backed up the tar. Kept symlinks and everything nice and happy. If you do that for each of your volumes, and you also have your config for running your containers like a docker-compose, congrats that’s all you need.

I don’t know who said you can’t just back up the volume, to me that’s kind of the point of docker. It’s extreme portability.

damn, RTL text is no trivial matter, kudos to them for getting that done

Ah, that makes sense. I didn’t realize we had asked for a new UI, here I was thinking we just wanted basic quality of life updates

Oh and make it FAST, no loading bars or spinners!

Wait there’s a community one?

I have lost now not hours, but days debugging their terrible AIO container. Live production code stored in persistent volumes. Scattered files around the main drive in seemingly arbitrary locations. Environment variables that are consistently ignored/overrided. It’s probably my number one example of worst docker containers and what not to do when designing your container.

It’s because with docker you don’t need to do log files. Logging should be to stdout, and you let the host, orchestration framework, or whoever is running the container so logs however they want to. The container should not be writing log files in the first place, containers should be immutable except for core application logic.

Persistent storage should never be used for logging in docker. Nextcloud is one of the worst offenders of breaking docker conventions I’ve found, this is just one of the many ways they prove they don’t understand docker.

Logs should simply be logged to stdout, which will be read by docker or by a logging framework. There should never be “log files” for a container, as it should be immutable, with persistent volumes only being used for configuration or application state.

I was just thinking yesterday - when was the last time we server owners actually had a feature update? I think last one I noticed was credits skip, and that was… 3 years ago? About?

Meanwhile Jellyfin apparently has been developing full steam ahead, I noticed credit skips in my test instance yesterday.

Ugh. Just

its_giving rizz ratios vibe;

No more needless nesting plz

Did they really? Oh my god please tell me your joking, that a company as modern as docker got a freaking oracle CEO. They pulled a Jack Barker. Did he bring his conjoined triangles of success?

Almost all of them. Forgejo handles containers already for example

And the permission of the peertube admins. A single channel on YouTube can easily be over a TB. Just casually dumping a TB or two of storage onto their wallets is going to cause them to notice.

Not crypto, blockchain. When done correctly and you don’t have every user trying to calculate the next hash for some pennies it works pretty well. Computing the hash when an action happens like a purchase is fairly trivial compared to mining.

Crypto started the concept of the blockchain, at the end though it’s just a distributed immutable audit log. The hash is required, but if done correctly, it’s trivial.

This is surprisingly one of the few actual useful uses of blockchain. Business tried to shove it in everywhere and it didn’t make sense because blockchain is a way to audit federated separate instances - which businesses are not. They’re a single monolithic structure, and they don’t need the trust - they already have it. They’re themselves, they just have to trust their own internal teams.

We, on the otherhand, are the perfect use for it. A way to say X person paid Y person for this product on this day at this time, X person now has the authority to rate Y person for how they did. Immutable, impossible to fake.

Can confirm, I host a very small instance with a few niche communities. Many subscribers, I don’t know of any defeds against me though. Plus it’s how I expect the fediverse to really grow naturally. Join a general one but then smaller instances of more niche topics. Kudos OP!

This person corpos

Boils down to how much are you willing to lose? Personally I do weekly