i would rather suggest to drop owncloud support altogether, nextcloud is a better alternative in each way. rather focus efforts where they can bring more benefits.
I just installed owncloud on VM Stretch with Lighttpd and faced several problems:
First of all about installation part: https://github.com/Fourdee/DietPi/blob/testing/dietpi/dietpi-software#L4005
owncloud meta package anymore, which in the past installed the actual owncloud-files and owncloud-deps containing apache and mysql. Now just owncloud-files is available (Stretch AND Jessie), so we need to take this. This is the reason why bbarker on DietPi forum didn't find any index file (actually nothing) of ownCloud 馃槈. (@Fourdee you could tell him to just manually install apt-get install owncloud-files as fast fix.)Second the configuration: https://github.com/Fourdee/DietPi/blob/testing/dietpi/dietpi-software#L8943
owncloud/data folder at the default place but symlinks it to DietPi userdata. This is okay as long as Apache is used and thus .htaccess is in place to block direct access to data folder.Otherwise ownCloud works fine. The fixes are not too hard, as we can copy much from Nextcloud installation. Also all the modules/webserver configs can be just copied. All still works the same for both solutions.
@molnarti
I would still leave the choice for users. I will check if not everything can be handled the same for both, besides the archive installation itself.
Confirmed, appears the .deb installation has changed, owncloud is now located in:
/usr/share/owncloud
EDIT: and a million other things as @MichaIng spotted 馃憤
Ok, i'll send PR to fix the install, however,
@MichaIng has made some good points, further investigation for improved installation is required, as a new ticket.
Tested fix with Odroid C2. Install working correctly.
Will mark this as closed. Ticket for improved installation: https://github.com/Fourdee/DietPi/issues/1229
i would rather suggest to drop owncloud support altogether, nextcloud is a better alternative in each way. rather focus efforts where they can bring more benefits.
@molnarti
Whilst I agree NextCloud is generally better. We do like to offer choice in DietPi (where possible) and let the user decide.
Most helpful comment
I just installed owncloud on VM Stretch with Lighttpd and faced several problems:
First of all about installation part: https://github.com/Fourdee/DietPi/blob/testing/dietpi/dietpi-software#L4005
owncloudmeta package anymore, which in the past installed the actualowncloud-filesandowncloud-depscontaining apache and mysql. Now justowncloud-filesis available (Stretch AND Jessie), so we need to take this. This is the reason whybbarkeron DietPi forum didn't find any index file (actually nothing) of ownCloud 馃槈. (@Fourdee you could tell him to just manually installapt-get install owncloud-filesas fast fix.)Second the configuration: https://github.com/Fourdee/DietPi/blob/testing/dietpi/dietpi-software#L8943
owncloud/datafolder at the default place but symlinks it to DietPi userdata. This is okay as long as Apache is used and thus.htaccessis in place to block direct access to data folder.We can just use this to automatically create database, user and correct data folder location.
Otherwise ownCloud works fine. The fixes are not too hard, as we can copy much from Nextcloud installation. Also all the modules/webserver configs can be just copied. All still works the same for both solutions.
@molnarti
I would still leave the choice for users. I will check if not everything can be handled the same for both, besides the archive installation itself.