Owncloud on freenas
Owncloud on freenas install#
I’ve just gotten to the point that ansible can automatically upgrade the packages of all my running VMs on various platforms (arch, ubuntu, bsd) and will install python2 or python3 if package not found since ansible requires this on the host to run more intensive tasks. I’m just recently into ansible so I’m learning. If I was smart I’d spin up an ansible script to actually be able to do some of these things automatically. I’ve actually applied some of the security tips to my other VMs (like aide for example). Dear FreeNas Friends, I have installed the plugin for OwnCloud and added storage under /media/cloud I wonder, how can I convince OwnCloud to actually use this. Lastly the guide I referenced has really good security tips near the end of the blog. FreeNAS can be implemented on commodity hardw. Again cool feature to have just very poor implementation by the collabora people Answer: FreeNAS is an unified Storage solution (it can be used as SAN and NAS if you configure properly) and NextCloud is an EFSS - Enterprise File Sync and Share Solution. I’ve tried both the docker image and the native installation and they both seem to have their own unique problems. Because FreeNAS is freebsd based and bsd in general has really bad support for Docker (Sorry RancherOS not a replacement), I needed to spin up an Ubuntu VM to try both options. It requires either a docker image or can be run natively on Linux. Most options are configurable on your Admin page, so it is usually not necessary to edit config/config.php. This document provides a more detailed reference. config/ lists all the configurable parameters within ownCloud, along with example or default values. directories (/usr/local/etc/rc.d), or is not executable. ownCloud uses the config/config.php file to control server operations.
![owncloud on freenas owncloud on freenas](https://2.bp.blogspot.com/-DYkaeagVv1E/V2qL6Gv1f2I/AAAAAAAAko0/xERxw1Kt9TQVEgcUkzwK0Wvsc4Lpus4KACK4B/s1600/%25E8%259E%25A2%25E5%25B9%2595%25E6%2588%25AA%25E5%259C%2596%2B2016-06-22%2B20.59.22.png)
lighttpd does not exist in /etc/rc.d or the local startup. I got to this part: rootowncloud2:/ service lighttpd onerestart.
![owncloud on freenas owncloud on freenas](https://2.bp.blogspot.com/-FxRuLd8uigY/VlTwF3mmoRI/AAAAAAAAGSY/i787DnGYWhU/s320/import1.png)
Click on the added Legacy Network Adapter (highlighted in the left pane below). Sadly, FreeNAS does not like the standard Network Adapter that is the default adapter in Hyper-V. I definitely would not rely on this feature if you absolutely require it. I tried to check if my lighttpd is running but it doesnt seem like it is. Next, select Add Hardware and Legacy Network Adapter.
![owncloud on freenas owncloud on freenas](https://i0.wp.com/gamblisfx.com/wp-content/uploads/2015/09/owncloud-on-freenas-9.3.0-finish.png)
Its a really cool potential feature however in my experience its super buggy and prone to breakage.
Owncloud on freenas code#
One thing you may want to really evaluate is collabora code if you need live on-line document editing. I’m currently in my testing phase which is going on month 2 for current nextcloud version. Try it for yourself but actually try for a couple of months and go through a couple of upgrade cycles prior to using it for mission critical things. There seems to be a lot of issues with it if upgrading. My entire experience with Nextcloud (Owncloud previously) has been really mixed.