Inspired by a blog post on Groovy Skills International I also upgraded my FreeNAS installation with my ownCloud 4.5. Advantage: with this, files can be synchronized automatically and are then available on different computers as well as over the internet with different smartphone apps or a web interface. The latter requires that the FreeNAS installation can also be accessed externally, which is only recommended if the system is really securely configured. However, the advantage is that by using the plugin jail, the actual IP of the NAS installation is not made externally available. If you want it for sure, you can use a separate jail for ownCloud.
At this point I do not want to go any further into the installation of ownCloud 4.5 at FreeNAS in the Plugin Jail - the aforementioned blog takes care of this very well. What got in my way was a missing configuration of the DNS server as well as a missing editor (besides vi, which I don't like :)). Both can be solved easily, nano can be easily upgraded via the FreeBSD ports.
The advantage of having your own solution: you are not dependent on the services of external services such as Dropbox, where data is always moved to the cloud and it is unclear whether it is really "secure" there - your own hard disks are then more trustworthy. Disadvantage: existing data cannot be transferred to the ownCloud - the system requires that the files can only be read and written by the web server user. This also means that the data in the ownCloud cannot be accessed without further ado, unless you use the corresponding user.
If you want to set up a FreeNAS system with your owncloud, you can do this on the basis of the HP Microserver N40L Shopping List for FreeNAS do.
English 
Deutsch 
Français 
Español
Thanks 🙂
If your "existing data" is in FreeNAS, you can mount it via WebUI into the ownCloud Jail.
Depending on the security concept it may be an option to set the rights to o+rwX and thus make them available.
Alternatively, you could also set the UID of the owner of the data (FreeNAS) to the UID of the www user (ownCloud Jail).
Have fun!
@ Dice
You mean via WebUI from FreeNAS to the jail? ownCloud complains to me if the rights are not 0770 - the only way is via the owner. I'll have to take a closer look this weekend.
@ Falk Jeromin
Yes, under _Services > Plugins > Management > Mount Points_ I append the path accordingly in _a subdirectory of *files*_. Example:
/mnt/path/to/files on /mnt/path/to/jail/usr/local/www/owncloud-4.5/data/dice/files/files
Perhaps your problem arises from mounting directly on the *files* directory.
(BTW v4.5.1 just released http://owncloud.org/changelog/)
I have designed a group permissions approach and published a manual on the subject:
http://groovy-skills.com/FreeBSD/2012/11/05/dateien-aus-freenas-in-owncloud-plugins-jail-verfugbar-machen/
That sounds very interesting 😉
you could also post this in the PBI Request Thread in the FreeNAS Forum,
that makes it easier for most people if it is implemented,
who have absolutely no idea what's on the console...
http://forums.freenas.org/showthread.php?137-Do-You-Have-a-Plugin-Request
Greetings
PS: Thought it was really cool that you mentioned my diary in one of your previous posts 😉
As soon as I have Internet in my new apartment, I will follow up on that. Also, if I can configure Wake-On-Lan over the Internet, in doubt a small Rasberry Pi will come behind the router with a surface, with which I can start the appropriate computers...
sounds also interesting 😉
@Dice: Nice How to, I sat down and installed Owncloud according to your instructions on a virtual system
everything was going great, really easy ... even I understood
Thank you very much for that !