The upgrade to version 13.0.0 fails due do wrong ownership of folder /usr/local/www/nextcloud/apps which should belong to user www. If this is not the case: - Upgrade fails using the command line to upgrade nextlcoud - Cron process fails To fix it: chown -R www /usr/local/www/nextcloud/apps Would be nice, if this could be corrected in pkg-plist. Thanks.
Hi Matthias, Actually it is slightly different. With 13.0 we changed the way this works. This is the FreeBSD port which should be managed from the ports infrastructure. I've added a number of nextcloud apps as ports as well that would fit into this structure, that is live in `apps`. The default for ports' Nextcloud should probably be: > 'has_internet_connection' => false, in config/config.php and/or adding another app-path which is set www-writable > array ( > 0 => > array ( > 'path' => '/usr/local/www/nextcloud/apps', > 'url' => '/apps', > 'writable' => false, > ), > 1 => > array ( > 'path' => '/usr/local/www/nextcloud/apps2', > 'url' => '/apps2', > 'writable' => true, > ), where the local nextcloud admin can store apps.
(In reply to Bernard Spil from comment #1) Dear Bernhard, thanks a lot for your clear explanation. I prefer to handle all apps/plugins in nextcloud itself as I use many of them. To maintain them all in the FreeBSD ports would be a lot of work which I think is not necessary. What do you think to keep the /usr/local/www/nextcloud/apps folder reserved for apps you install from inside nextcloud using there app store and use a dedicated folder like /usr/local/www/nextcloud/freebsd_apps for all apps you install using ports? With this setup you would not break the documentation available by nextcloud but you can then separate it better?
(In reply to Matthias Fechner from comment #2) Isn't that exactly what the patch does?
(In reply to Bernard Spil from comment #3) Sry Bernard, I have not checked to referenced PR. Yes the referenced PR does exactly this, so please continue ;)