If you're running @nextcloud on #fedora, you'll want to upgrade to #Nextcloud 24 before upgrading to Fedora 36 or else you'll get a php compatibility error. I was able to hack the versioncheck.php to override it and upgrade to 24 and then everything was OK, but you'll have a much easier time upgrading nextcloud first.

@vwbusguy @nextcloud thanks for the heads up, I was just going to upgrade to F36 still being on NC23.

@sesivany @vwbusguy So you either run super fresh Fedora on your servers or you run Nextcloud server on your desktops. Why do you do that?

@albi @vwbusguy
I have had Fedora on my personal server with quite a few services for 5 years and basically no problems. It's better for me to spend 1 hour doing a flawless upgrade every 6 months than doing a major and difficult upgrade every 3 years with some LTS distro.

@sesivany I hear you. I HATE migrating shit from an old CentOS to a slightly less old one every few years at work.

@albi @vwbusguy @sesivany

@sesivany @albi I've kept this nextcloud box going since 2014 (when it was owncloud) running on commodity second hard hardware and keeping Fedora continuously upgraded.

@sesivany @albi @vwbusguy The advantage of Fedora is too great, this is why I stick to it too. However, just like in case of PHP upgrades are not always seamless. In my case the issue is the DB format migrations in Postgres. Every time I upgrade, I get ready to restore, because once in a while the new server refuses to read the old DB. Then, "postgresql-setup --upgrade" is equivalent of hacking versioncheck.php. The manual for the tool even warns that it does not always work!

@pro @albi @sesivany I run mariadb for my db backend and it's survived the upgrades just fine.

@vwbusguy @pro @albi the same here, MariaDB has been just fine through the upgrades.

@sesivany @albi @vwbusguy I upgraded about 50x Deb 10 -> 11 servers. 15min - 2h per server, ~45min average. Release cycle 2y.