Scrubbles

Docker compose in git. Env in 1password or whatever password manager you use. Most support uploading a raw file.

I mean, you’re right here.

Thank you I thought I was going insane. It’s not Reddit levels of activity, but I’d say this is pretty dang active. Stats on the right show almost 600 users a day, ~7k a month, almost 100k comments…

Great callout, thanks for posting

Yeah it’d be a LOT of constant wireshark and reverse engineering to figure out every API it calls. Then probably something in the middle to sit on the host, need to figure out https certs since you’d be spoofing the host, and of course making sure you get the responses absolutely correct.

Not impossible, but it’s not trivial anymore either.

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?

That doesn’t make up for bad container decisions. I run much more complex containers both that split out responsibilities and that contain everything as one container. The size and complexity is irrelevant to the bad design decisions. You can have an image that eats up gigabytes of space that runs off of proper environment/config variables with properly mounted volumes.

I mean, it’s a valid reason. I originally joined Discord back in 2016 because of it’s easy to use voice. It became the standard for voice chat. Before that I had been using the Xbox party chat and other garbage voice systems.

Matrix doesn’t offer the same experience as discord. I’m sorry but it doesn’t. I set up my own to compare to see if my friend group would like it, and it was quite a step backwards. Even in it’s best platform element it was missing a lot of stuff from discord.

So, things like this I’d be very interested to watch. Revolt looked the most promising but it didn’t offer federation, and I wasn’t going to make everyone have a separate accountjust for our server

So this will be interesting. I will need at least voice to get them to come over, but I’ll watch this project closely

Yeah I’ve thought about migrating, but I have a few users on it who use nextcloud regularly now, so I’m forced to support it - unless there’s an easy migration path

Docker images should never self update - that’s an anti pattern. They should be static code. The only time I would expect a docker image to “auto update” is if I was using the “latest” or “stable” tag and Compose/Kubernetes/I repull the image - but the image should never update itself.

Yes, OP bit off more than they could chew. Nextcloud, however, is breaking the entire purpose of Docker images by having an auto-updater at all.

I had to learn how to mount subpaths for their terrible container, and god just the updater is mind boggling. And I have to store their code in a volume, because of course I have to, why would code and configuration ever need to be… configurable? I actually just tried to put their config.php into a ConfigMap just to try, and of course PHP doesn’t allow that - not that I blame PHP for it - but ffs it’s been years, it’s time to allow config to also come from a yaml or something.

I do it in docker at home, for myself, in an environment I am okay with accidentally destroying - and even then I have nightly backups of the volumes.

In a professional system, as mentioned in my other comment, I would simply just do it in a VM with the disk scheduled also for nightly backups. Nextcloud just hardcoded too many things dependent on thinking the underlying system was mutable. Unfortuantely that’s just the easiest way to handle it.

However, also as mentioned, if I were in a professional environment, I’d have to really look at the cost for all of that infrastructure and my time to run it - and decide if I really thought I could run it myself with all of that overhead, and that it would still make sense compared to just doing google docs or something. Remember it’d be my ass on the line, as OP is learning

Oh, Nextcloud docker is a joke. They follow no standards or best practices when it comes to docker. They keep the entire app directory mounted as a volume, which means it does upgrade you without you “needing” to upgrade the docker image. They have volumes within volumes they need to mount. Their configs can (and do) override environment variables. Most actions that need to be taken require running an occ command which can only be done by exec’ing into the container.

Nextcloud docker is honestly just such a joke. They should have rethought their application from a docker sense and they didn’t. God just number one - Docker images should never update. It’s a freaking pinned version for a reason. If I want to update, it should be as simple as upping the version tag, and it does any upgrades in place when I do that.

I honestly steer people away from Nextcloud now because of how mismanaged their images are.

Second there. Running kubernetes at home is great - to learn it for work.

If you don’t need to use it for work then you’re going to spend weeks if not months setting it up for very little payoff at home