Is someone working on Nextcloud 16 support? I think there might be a problem with Debian Stretch since we will need php version 7.1 or later for Nextcloud 16. Please let me know what you think.

Jeremy Davis's picture

We do intend to build an updated appliance soon(ish) but I don't have a clear ETA. However, it's worth noting that you should be able to update Nextcloud fairly easily as per their docs.

Also, I suspect that you originally wrote a body to your post, but the spam filters blocked it (they can sometimes be a little aggressive and yet still some spammers manage to get through...). So I have tweaked your user account to avoid most of the spam traps.

One thing that got lost in the spam filter: Nextcloud 16 requires at least php7.1, but Debian Stretch is on version 7.0 (EOL 1st of December). That's why you cannot upgrade that easily on Stable.

Jeremy Davis's picture

OK, thanks for the heads up on that! :)

So, that may well delay the release of an updated appliance providing Nextcloud v16.0.

Whilst Debian provide backported security updates for PHP7.0 (so the fact that it's EOL upstream isn't really an issue), many apps have moved on and now require PHP7.1+. Until Debian Buster goes stable (sometime mid year? - will include PHP7.2) we'll likely make do by installing a newer PHP version (most likely PHP7.2) from FWIW he's one of the main PHP package maintainers for both Debian and Ubuntu, so we're in good hands there.

My plan is to actually include the components in all LAMP/LAPP based appliances, but leave it disabled by default (unless required, e.g. by Nextcloud). That would allow other apps (that currently only require PHP7.0) to stick with PHP from stable, but provides an upgrade pathway for apps that will require a newer version in the future. That would make it relatively easy for users to update themselves too if/when required.

That sounds like the ideal way to go. Thanks for the reply.

It builds on Debian 9 and uses PHP 7.3 from Maybe that's the easiest way to create a Nextcloud 16 machine with an A+ rating.

Jeremy Davis's picture

Thanks for sharing the link. I'l have a look over the script and see what it does and if they're doing anything we're not (that we think is a good idea), then I'll implement it into our buildcode. I must say that I don't envy him trying to maintain multiple bash scripts totalling ~2500+ lines. That must be a massive pain!

Because we have a library of ~100 appliances and some of the others will need newer PHP too, it makes much more sense for us to maintain our existing buildcode. FWIW the way that our buildtools are set up, all the shared code is in a separate repo. So for example the code to install an alternate version of PHP (we're currently using 7.2, but we might instead go for 7.3) will only need to be written once and multiple appliances can inherit it. There is some stuff in that script you shared (FWIW the actual scripts are here) that I wouldn't do in our appliances, but there is some interesting stuff (like a fix for an issue I wasn't aware of!).

Thanks again for sharing! :)

Add new comment