69
submitted 2 days ago by [email protected] to c/[email protected]

And it failed spectacularly.

We only needed a simple form, but we wanted to be fancy, so we used "nextcloud forms".

The docker image automatically updated the install to nextcloud 30, but the forms app requires nextcloud 29 or lower. No warning whatsoever. It's an official app, couldn't they wait that it was ready for NC 30 before launching it? The newsletter boasts "NC hub 9 is the best thing after sliced bread" yet i don't see any difference both in visual or performance compared to NC hub 2

Conclusion: we made our business to rely on nextcloud forms as a signup form, but the only reason we were using it was disabled who knows how many weeks ago.

top 50 comments
sorted by: hot top controversial new old
[-] [email protected] 11 points 16 hours ago

Docker automatically upgrades if you tell it to by specifying "latest" or not specifying a version number. But it only upgrades if you issue the pull command or the compose up command. There are ways to start without a pull like using start or restart. So yes, there was warning and something you did actively told it to upgrade.

And it's really bad practice to update any software without testing, especially between breaking/major version numbers.

Finally, it's not uncommon for a platform to release its update and then the plugins or addons to follow. Especially with major updates that require lots of testing before release. This allows plugin/add-on makers to fully test their software with the release version of the platform rather than all of the plugin makers having to wait for one that may be lagging behind.

[-] [email protected] 11 points 21 hours ago

Why did you do automatic updates without testing? That is the real issue.

Honestly your IT department sounds like it could use some help

[-] [email protected] 1 points 14 hours ago

take a VM snapshot, upgrade the app, validate it still works as intended, if not, revert from snapshot

[-] [email protected] 1 points 18 hours ago

The forms app is useless. It's basically for surveys. I can't see how you'd use it for signups.

[-] [email protected] -1 points 16 hours ago

I wrote signups but I meant survey (in another comment I wrote "I would have never checked the useless survey")

[-] [email protected] 19 points 1 day ago

Specify a Version Tag in docker compose and update nextcloud deliberately through the webapp, that way it doesn't update automatically on a pull

[-] [email protected] 3 points 21 hours ago

You can't update it in the web app. You need to do a docker-compose pull followed by docker-compose up -d

[-] [email protected] 31 points 1 day ago

Backups and rollbacks should be your next endeavor.

[-] [email protected] 8 points 21 hours ago

Seems easier to blame Nextcloud

load more comments (1 replies)
[-] [email protected] 74 points 2 days ago

Wait, you update productions systems without running a staging environment? Or even checking the update notes and your installed apps? Also no backups? What kind of business are you running over there?

[-] [email protected] 4 points 21 hours ago

One that lacks a good IT department apparently

[-] [email protected] 52 points 2 days ago

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.

[-] [email protected] 1 points 21 hours ago

The images work fine for me. The problem is that Nextcloud is a complex app that doesn't really work with the design of one container to do one job. It is pretty much a regular application that uses docker for packaging.

[-] [email protected] 1 points 21 hours ago

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.

[-] [email protected] 2 points 21 hours ago

Again there docker image is just a packaging format and a health check. I very much wish it were better but for now it works

[-] [email protected] 1 points 19 hours ago
[-] [email protected] 12 points 2 days ago* (last edited 2 days ago)

Yep, and I'd guess there's probably a huge component of "it must be as easy as possible" because the primary target is selfhosters that don't really even want to learn how to set up Docker containers properly.

The AIO Docker image is an abomination. The other ones are slightly more sane but they still fundamentally mix code and data in the same folder so it's not trivial to just replace the app.

In Docker, the auto updater should be completely neutered, it's the wrong way to update the app.

The packages in the Arch repo are legit saner than the Docker version.

load more comments (5 replies)
load more comments (4 replies)
load more comments (7 replies)
[-] [email protected] 29 points 2 days ago

The docker image automatically updated the install to nextcloud 30, but the forms app requires nextcloud 29 or lower.

Lol. Do not blame others for your incompetence. If you have automatically updates enabled then that is your fault when it breaks things. Just pin the major version with a tag like nextcloud:29 or something. Upgrading major versions automatically in production is a terrible decision.

[-] [email protected] 17 points 2 days ago

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.

[-] [email protected] 17 points 1 day ago

If you say

Thing:latest

and then redeploy your compose file or what not,

well, you're getting the latest!

load more comments (5 replies)
load more comments (4 replies)
load more comments (7 replies)
[-] [email protected] 0 points 22 hours ago

I pretty much use NextCloud as just a storage device and nothing else. Using anything in the actual UI is just atrocious and the apps are not updated or just outright abandoned, and can't be relied on.

[-] [email protected] 1 points 16 hours ago

Us too, we only use it as a filelink provider for thunderbird and to host a useless survey that's going to get filled once a quarter. That's why nobody noticed the survey was disabled and that's why we're not doing multistage testing in multiple virtual machines. We are a super small company and ok with something that one day can be 3 days offline. Otherwise it would be cheaper to pay $100 to Surveymonkey and $100 to Dropbox

[-] [email protected] 1 points 21 hours ago

I disagree. I use and depend on the apps including things like calendar and talk.

[-] [email protected] 2 points 21 hours ago
[-] [email protected] 3 points 21 hours ago* (last edited 21 hours ago)

1000004635

YOU CAN'T DO THAT

load more comments
view more: next ›
this post was submitted on 24 Sep 2024
69 points (84.2% liked)

Selfhosted

39327 readers
1661 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS