Yep. RAM usage. You just saw firsthand why I've advocated against going with MYSQL for the plugin. Quite a few have asked for MySQL to be in the plugin. The problem is that you either accept the small home users (and don't go with mysql) or you cater to the larger enterprise users (who *love* to get enterprise stuff for free) and alienate those small home users who might be forced to buy more RAM just for the sake of a plugin. Several people have asked for the plugin to be recreated for MySQL so they can use it for large scale enterprise deployments. I always told them "fine, pay someone to setup your Owncloud server instead of trying to bend a little plugin that really is designed for home users". If you look in bugs.freenas.org there's probably a few tickets that have been closed over the last 2 years where I advocated against it and successfully won. My opinion is that plugins should be for small office and home users. Those people won't need something that is big and fat like mysql, and they will see only downsides to the switch. Enterprises really shouldn't be relying on plugins anyway, and if they are they are a fool for doing so (in my opinion).
So choose wisely! The plugin's future depends on you deciding who you want to cater to. ;)
That's what I'm struggling with. I've gotten to the point I have a decent OC8 plugin using apache(and sqlite).
Gonna ask around, but one idea someone had before was having an owncloud-mysql alternative.
Agreed about the reliablilty, the current PBI/API implementation are fine for my MediaBrowser jail, but for my personal ownCloud I wouldn't rely on plugins and rather run it in a jail from source.
####
One other dilemma I have is if I include libreoffice for DOC(X) editing/(pre)viewing. Including it makes the plugin go from 96MB to 188MB, and that's highly compressed. That means if I ever do have to push an update through FreeNAS it's going to take forever and probably fail.