68
I tried to selfhost Nextcloud at work
(feddit.it)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 24 Sep 2024
68 points (80.4% liked)
Selfhosted
40767 readers
1587 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 2 years ago
MODERATORS
Why did you do automatic updates without testing? That is the real issue.
Honestly your IT department sounds like it could use some help
Manual docker upgrade issued my me after reading the official blog and newsletter. The upgrade notes described the new version as the best thing ever and didn't mention that one of their selling points would be disabled without any notice.
I'm starting to see a pattern in those comments like "why did you wear a skirt that night? It looks like you asked for it..."
Whoah, dude.
Not only are you being told what could have and will ward off unplanned breakage, but you have somehow characterised yourself as an unsuspecting victim here? Inaccurate and really inappropriate comparison.
You knew enough to take on deploying a service, now comes the grown-up part where you hedge against broken updates.
I don't know if maybe it's my bad english in explaining it or it's your comprehension skills that lack something.
I write it again for the 10th time: I'm 100% ok having 1-2 weeks of downtime, and this is why i do it live. It simply doesn't make sense to dedicate several hours every month on testing if all i need is getting 3 useless surveys filled per year. If it was essential for work and i needed 99.99999% uptime i would directly subscribe typeform or surveymonkey. If tomorrow my install completely bricks and disappears in thin air, i would have lost 30 minutes of time and no valuable data. I literally spent more time designing the logo for the instance than managing it. This is just to state how unimportant the data stored on it.
This post wasn't made about "oh no i lost millions and all my irreplaceable data thanks to nextcloud stupid updates" but how stupid is to release something that breaks features that they're using as selling point.
ok, now that we established that my IT skills are lacking and i should be fired because one single survey couldn't be filled, this is the release notes: https://docs.nextcloud.com/server/latest/admin_manual/release_notes/upgrade_to_30.html
Please tell me where they say that this feature is automatically disabled and also tell me why you think that this is acceptable.
I don't understand why you think that is acceptable.
I even can't find other examples where a release is so rushed, that selling points are disabled without ETA. I never saw for Libreoffice 24 dropping support for opendocument files for a couple months just because they had to meet a self imposed deadline
Cute victim mentality, but gross and insanely wrong comparison
Learn from your mistake and don't update without testing next time, it's 100% on whoever updates the production environment to make sure that shit isn't broken for whatever reason before pushing it customer-side
It's more like you bought a random white powder from your dealer without asking what it was and are now upset you almost died
ok, please tell me where in the release notes they say that the forms app will be automatically disabled without warning after update, thanks https://docs.nextcloud.com/server/latest/admin_manual/release_notes/upgrade_to_30.html
Literally just googled "nextcloud forms" and looked at their supported versions and whaddya know, it says right on that webpage that there's no stable version for 30 yet, so safe bet would be that it wouldn't properly work when upgrading:
There is a supported nightly build, though, so you could probably have tried that
It's on you to look up what will break when you update, or to test and see what happens when you do. A major update page isn't going to list all of the things that rely on it that break because that's fucking unreasonable
go to watch who is the maintainer of nextcloud forms, then see if they could have known that NC 30 was about to go out or not
It's definitely not unreasonable that if I make product X and I make product Y, and they're not compatible, then a bit of warning is suggested.
Again, wordpress updates break plugins all the time, but automattic plugins (same people of wordpress) never break. Coincidence? They just launch a new wordpress without checking if woocommerce or jetpack don't work?
Which was given by the app that gets broken by the update
Windows doesn't tell you that upgrading to 11 will break x, y, and z that you have installed, you're expected to go to the sites for those programs and check if they work. Same exact idea
The same company making both apps is never a guarantee that they'll play nice day 1, for many reasons
I'll repeat: learn from your mistake instead of blaming other people for your naivete. If an app is important and might break during an update of something: check the apps documentation to see if it supports said update
Ok i get it, it's best practice to do rushed releases without QA because users are the free testers.
They definitely had no way to know that their own app was incompatible, this is definitely a problem of the stupid user. Idiot user who believed their newsletter "update now, hub 9 is the best thing ever". The user should have known that stable = untested beta
Also, this issue happened exclusively to me in the whole world, because everyone else isn't an idiot like me and checks 30+ release notes scattered in 30 different repositories to guess any incompatibility. I was lazy and only checked the main notes! Such an idiot! Why I didn't check every single installed app? It's just 30! Nextcloud devs couldn't have known that nextcloud devs didn't update the manifest of the forms app! I should have checked before! Completely my fault!
Now if you excuse me I got an update to the Windows nextcloud desktop app and it must reboot after update because reasons even if there's a GitHub issue with 200 angry comments about that. No wait! Stupid me! First I have to fire a VM and use a whole week to write automated tests that account for every possible combination of settings, language, power management, installed apps and so on. Otherwise I could lose a worthless survey that nobody reads and that will definitely get me fired!
You literally used the wrong version. As I stated: the app you're talking about clearly states it does not have a stable release for the version of nextcloud you're running.
They knew, and told you, right on the app page
You said it, not me. I tried being nice but that really is what happened: you fell for what the marketing team wrote and skipped basic IT steps in doing so. Now, rather than just admit you made a mistake that a LOT of people have made (including me, I'm a fucking idiot too) you are whining and doing your best to me talk gymnastics this into you being a victim of something
How you managed to convince your IT department of anything with a knowledge that shallow and an attitude like that I'll never know. Grow up.
When on my personal install the music app was broken after an update for months, I didn't complain at all. Because I went to see who was the maintainer: owncloud. Not their fault. In this case was my fault. Definitely my fault and without sarcasm. A third party plugin is expected to have problems after updates. Completely understandable. They're even competitors.
First party plugins instead, MUST work at all times versus the latest stable release. It's the reason I didn't check compatibility.
This is the concept I want to say. It's not hard. I'm not saying "the update process must be idiot proof". When shit like this happens, it completely erodes trust in users. It's not stable, it's beta. It's a tiny detail. It's just a number on the manifest. What does it cost to update that number to 30 for the forms app? (The "incompatible" version runs perfectly fine when the check is overridden)
But no, let's defend this behavior of moving fast and breaking things for no reason, like that issue thread on GitHub where users are rightfully pissed that the Windows nextcloud desktop client reboots without confirmation and fanboys are dismissing it "eh the cloud indicators in explorer.exe are so important, must reboot at all times, what's the problem"
Do you agree that first party stuff must work? (unless it's discontinued)
Would you expect Microsoft Office 365 being disabled after upgrading to Microsoft Windows 11?
And finally, how I persuaded the it department. Here I make a list of all the members:
We were just searching a way to host a worthless survey that nobody is watching instead of paying $350 to Surveymonkey. We drank the marketing cool aid and assumed that something heavily promoted just 6 months ago would be supported. But this is unreasonable.
Solution 1: waste a week doing your suggested way of multiple installs and custom unit tests and every quarter check carefully everything because nextcloud "stable" is as stable as a house of cards.
Solution 2: delete nextcloud and write a form in PHP+HTML in an afternoon, don't have the same problem with nextcloud 31 next quarter.