Well, I think nobody can guarantee that it is “totally safe”. Never change a running system…
I had a lot of trouble with dist-upgrades and Ubuntu in the past that ended up with a fresh installation.
If you work in a virtual environment then you could test “risk free” wtih a snapshot of the actual state.
Or you could image/clone the system if is a physical one.
Why not give the docker container a try? You would never again have issues like this. You can even try to make the move with your existing box (after disabling whatever web server you currently have on, whether be apache or nginx).
Not sure how familiar you guys are with docker, but it is basically an operating system virtualization engine, not to be confused with full virtualization though. Think of it as more like sand-boxing. You install containers, which have all the software they need to run whatever task they have. This allows you to run full stacks of containers that will run exactly the same no matter what OS you have.
For example, in @tiripon’s case, he can be running the latest Nextcloud 15.0.2 with an alpine or debian OS in its container, but his host OS will remain Ubuntu 16.04. When and if he decided to upgrade his host server, he simply moves all the docker persisted files and container definitions, and boom, the exact same Nextcloud will be running in minutes. I know I am putting it in too simple terms but that is exactly what it does.
In terms of resource utilization, the overhead is very negligible.
After the 15.0.2 update (from version 15.0.0), overwrite.cli.url no longer evaluates. I run a server on xxx.de and externally I speak it on yyy.de. But only every URL is converted to xxx.de / … Until version 15.0.0 the URL was always yyy.de / …
@tiripon: it’s not nextcloud, it’s apache: you need to configure your virtual server to use the right version of php; and possibly apply any custom configuration you have in your php7.0 php.ini over to the new php.ini
@Traceman : make sure your overwrite.cli.url ends with a slash, I found there were issues with the occ CLI - htaccess command unless it had it - I know it’s not related but it could be a part of your issue
I don’t know why I received this, but I am running Mac OS 10.14.2 with PHP 7.2.12 and NextCloud 14. I do plan to upgrade to 7.3.x, soon. I also have this on Linux Mint 19, but that machine will be shutdown soon.
This is getting too complicated. I was expecting the upgrade to go smoothly. I don’t understand why it causes so much problems (I did not even start to troubleshoot the second message I got about “Missing index”)
A little bit disappointing.
I will put back my backup and leave it on version 14.
Has NC updated its documentation? 7.0 was the only version that officially associated with NC. While 7.2 was possible with odd workarounds. It would be great to know the official position now. These kinds of issue raise the question as to whether NC is “a safe place for all of your data”