[bug]: Update to current version

[tflidd]

Prerequisites

• I have searched for existing issues that already report this problem.

Device

Laptop/Desktop

Device OS

Windows

Device OS Version

10

Browser

Firefox

Browser Version

134.0

Current Behavior

On your marketplace, you ship Nextcloud version 27.1.4:
https://marketplace.start9.com/nextcloud

Which is an outdated Nextcloud version (https://github.com/nextcloud/server/wiki/Maintenance-and-Release-Schedule) with known security issues: https://github.com/nextcloud/security-advisories/security/advisories

Expected Behavior

Ship a supported Nextcloud version. Provide instructions for users how to update/upgrade.
Your users don't know how to handle this: https://help.nextcloud.com/t/do-i-need-to-actually-update/214814

Steps to Reproduce

1. Install nextcloud app
2. it is out of date

Anything else?

No response

[joshtrichards]

Hi Start9!

I'm one of the helpers over at the @nextcloud open source project. One of the things I help out with over there is the micro-services image.

Looks like Start9's marketplace image for Nextcloud is derived from the @nextcloud project's micro-services image.

That's great!

But a couple notes:

• Nextcloud Server (and, in turn, the upstream image you're using) gets updated roughly once a month via a maintenance release (i.e. fixes for critical bugs and security matters).
• It's important users stay up-to-date on the latest maintenance releases.
• Also, approximately every 12 months the oldest major train still receiving maintenance (i.e. v29, v30) reaches its end-of-life and no longer receives further bug fixes. We're currently supporting v29 and v30. Both v27 (what your wrapper image is using) and v28 have reached end-of-life.
• Unfortunately Nextcloud environments can't skip major releases, so when you do upgrade your wrapper image, you'll need to offer your user base first v28 (even though it's end-of-life) then v29.

The good news is that the monthly maintenance releases (i.e. the last digit: 29.0.5) require nothing more than a counterpart version bump in your Dockerfile in 99% of cases so those shouldn't take much work. You may even wish to semi-automate it.

You can subscribe to receive notices of new upstream image releases from our github repo: https://github.com/nextcloud/docker/releases

For major version bumps (i.e. v27 -> v29) there are sometimes breaking changes that can require adjustments to surrounding suggested web server configurations, etc. Fortunately, if you're sticking with our default image variant (Apache based), you are usually pretty covered in this area automatically. Even so, these types of changes are documented in a special Critical Changes section of our Admin Manual in case you wish to check them before pushing major version bump via your marketplace.

If I can help, let me know.

[kn0wmad]

Hi Start9!

I'm one of the helpers over at the @nextcloud open source project. One of the things I help out with over there is the micro-services image.

Looks like Start9's marketplace image for Nextcloud is derived from the @nextcloud project's micro-services image.

That's great!

But a couple notes:

* Nextcloud Server (and, in turn, the upstream image you're using) gets updated roughly once a month via a maintenance release (i.e. fixes for critical bugs and security matters).

* It's important users stay up-to-date on the latest maintenance releases.

* Also, approximately every 12 months the oldest major train still receiving maintenance (i.e. v29, v30) reaches its end-of-life and no longer receives further bug fixes. We're currently supporting v29 and v30. Both v27  (what your wrapper image is using) and v28 have reached end-of-life.

* Unfortunately Nextcloud environments can't skip major releases, so when you do upgrade your wrapper image, you'll need to offer your user base first v28 (even though it's end-of-life) then v29.

The good news is that the monthly maintenance releases (i.e. the last digit: 29.0.5) require nothing more than a counterpart version bump in your Dockerfile in 99% of cases so those shouldn't take much work. You may even wish to semi-automate it.

You can subscribe to receive notices of new upstream image releases from our github repo: https://github.com/nextcloud/docker/releases

For major version bumps (i.e. v27 -> v29) there are sometimes breaking changes that can require adjustments to surrounding suggested web server configurations, etc. Fortunately, if you're sticking with our default image variant (Apache based), you are usually pretty covered in this area automatically. Even so, these types of changes are documented in a special Critical Changes section of our Admin Manual in case you wish to check them before pushing major version bump via your marketplace.

If I can help, let me know.

Hey there,

I'm working on a v28 update, and have a short list of clean up issues I am trying to address. At first I thought the problems were with nginx conf, but have not had luck there. Issues listed in the PR, any suggestions would be much appreciated!!

[kn0wmad]

Hi Start9!

I'm one of the helpers over at the @nextcloud open source project. One of the things I help out with over there is the micro-services image.

If I can help, let me know.

Hey Josh,

You asked if you could help, and I could really use some. I'm working on the v28 update, hopefully immediately followed by a v29 update, and have several questions that I'm struggling to find answers for between your docs, forums, and github. Is there any way we could chat about these? StartOS is a bit different and it would be tremendously helpful to have someone who is deeply familiar with the nextcloud architecture to get this back on track.

Thanks for your time