Open oparoz opened 8 years ago
i could not respond to your topic on the owncloud forum, so i do it here :). I tried to install your option 3.
I sideload the option 3 amd64 .snap in a virtualmachine. But the install seems to fail (running ubuntu 16.04 amd64)
test2@test2:~$ sudo snap install /home/test2/Downloads/owncloud_9.0.1interfasys1_amd64.snap [/] Make snap "owncloud" available to the system error: cannot perform the following tasks: Make snap "owncloud" available to the system ([start snap.owncloud.php-fpm.service] failed with exit status 1: Job for snap.owncloud.php-fpm.service failed because the control process exited with error code. See "systemctl status snap.owncloud.php-fpm.service" and "journalctl -xe" for details. )
test2@test2:~$ systemctl status snap.owncloud.php-fpm.service ● snap.owncloud.php-fpm.service - service php-fpm for snap owncloud - autogenerated DO NO EDIT Loaded: loaded (/etc/systemd/system/snap.owncloud.php-fpm.service; enabled; vendor preset: enabled) Active: inactive (dead) (Result: exit-code) since zo 2016-04-24 20:29:14 CEST; 20min ago Process: 2764 ExecStart=/usr/bin/ubuntu-core-launcher snap.owncloud.php-fpm snap.owncloud.php-fpm /snap
apr 24 20:29:14 test2 systemd[1]: Stopped service php-fpm for snap owncloud - autogenerated DO NO EDIT. apr 24 20:29:14 test2 systemd[1]: Starting service php-fpm for snap owncloud - autogenerated DO NO EDIT.. apr 24 20:29:14 test2 systemd[1]: snap.owncloud.php-fpm.service: Control process exited, code=exited stat apr 24 20:29:14 test2 systemd[1]: Failed to start service php-fpm for snap owncloud - autogenerated DO NO apr 24 20:29:14 test2 systemd[1]: snap.owncloud.php-fpm.service: Unit entered failed state. apr 24 20:29:14 test2 systemd[1]: snap.owncloud.php-fpm.service: Failed with result 'exit-code'. apr 24 20:29:14 test2 systemd[1]: snap.owncloud.php-fpm.service: Service hold-off time over, scheduling r apr 24 20:29:14 test2 systemd[1]: Stopped service php-fpm for snap owncloud - autogenerated DO NO EDIT. apr 24 20:29:14 test2 systemd[1]: snap.owncloud.php-fpm.service: Start request repeated too quickly. apr 24 20:29:14 test2 systemd[1]: Failed to start service php-fpm for snap owncloud - autogenerated DO NO
Thanks for testing @bonsje . Unfortunately, these snaps don't work yet with the desktop or server versions of Ubuntu because we're using Ubuntu Core to test these images and that hasn't caught up yet. So for now you have to test using the older base images of Core linked in the post in the forums.
Hi Olivier,
Will the snap packages be compatible with the new Ubuntu core (16.04) soon ? Or is this not easy possible because the Ubuntu snappy core uses a older base (never used ubuntu snappy core).
For input that you are asking about the Option 1/2/3 in the own cloud forum. I think option 3 will be the best, because we need the possibility to hack the configs of Apache2/php and owncloud itself.
2016-04-24 20:57 GMT+02:00 Olivier Paroz notifications@github.com:
Thanks for testing @bonsje https://github.com/bonsje . Unfortunately, these snaps don't work yet with the desktop or server versions of Ubuntu because we're using Ubuntu Core to test these images and that hasn't caught up yet. So for now you have to test using the older base images of Core linked in the post in the forums.
— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub https://github.com/owncloud/pi-image/issues/34#issuecomment-214022831
Met vriendelijke groet, Wesley Bons
Will the snap packages be compatible with the new Ubuntu core (16.04) soon ? Or is this not easy possible because the Ubuntu snappy core uses a older base (never used ubuntu snappy core).
Oh yes-- the Snappy development team was recently focusing on the desktop. As soon as that work trickles back into Ubuntu Core that's what we'll be using.
Thanks for the feedback @bonsje!
The main advantage of Snappy from my pov is that the OS and platform/stacks can be automatically updated and secured remotely. Some users will not like the current level of micro-management found in the ownCloud snap, while newcomers and fans of set-and-forget appliances will love it.
Current snap
UX type: Using a ready-to-use service or software, with the advantage of storing data locally, on owned hardware
Limitations
.htaccess
is read-onlySome of these limitations can be lifted either by Ubuntu or ownCloud, but it will take some extra work by community maintainers and the result may not be set up the way you want. Overall, I'd say that ownClouders have less freedom with this solution and fixes will take a long time to land.
Advantages
Alternative
UX type: Using a fully managed VM or hosting space
Conclusion
I think the WD PiCloud can target different markets. People who want to dump their photos to their device and rely solely on the GUI and the sync clients will love the current snap, but anybody with slightly more complex requirements will get frustrated, especially when seeking help from forums or Github since most tips won't work.
I don't know who WD had in mind, so I don't know which solution is the best fit for their marketing plan. It's very probable that someone will release a LAMP snap and then anybody could install ownCloud on it, but just like users can pick a generic VM as their base, the experience is much nicer when they pick the official ownCloud VM, so it might be worth offering an alternative with full read-write access to ownCloud.
@jospoortvliet @enoch85 @kyrofa