Seafile with Chwala

[Troy Carpenter]

I am revisiting this now that 3.4 is out with Seafile support in Chwala.
Unfortunately, I haven't been able to figure out how to configure it.
First, let me give a bit of info out of the way:

1. Kolab 3.4 on Centos, with the latest packages as of this writing (see
email timestamp).
2. Seafile 4.0.6 is configured and running under apache with https support.
I have not used a client with it other than the web interface, but
everything seems to be working.  I have configured LDAP and that is working
(I've been able to sign in as a few Kolab users without pre-configuring them
in Seafile).

I've looked at the chwala files in github, and on my server.
/usr/share/chwala has most of the same directories, but most are links into
the Roundcube config structure.  Specifically, the config directory with the
sample config.inc.php file is actually a link to /etc/roundcubemail, and
config.inc.php.dist is nowhere to be found.  Neither are some of the other
support directories, like the README.md file and the SQL files in doc.  I
have executed the SQL file against my Kolab MySQL database, and have
confirmed that the changes are there.

Where do I put the chwala config file?  Do I simply add the configuration
commands to Roundcube's config.inc.php file?  The readme file doesn't really
provide all the info for configuring Seafile and really seems geared toward
configuring a new chwala driver.

Any help would be appreciated.  Given this is a feature that has been touted
in the release notes and on the blogs, I would have expected to find
instructions on switching the files storage from IMAP to Seafile.

-----Original Message-----
From: users-bounces at lists.kolab.org [mailto:users-bounces at lists.kolab.org]
On Behalf Of Aleksander Machniak
Sent: Friday, December 12, 2014 10:58 AM
To: users at lists.kolab.org
Subject: Re: Seafile with Chwala

On 12/12/2014 07:20 PM, Franz Skale wrote:
> i checked out the git repo too, but didn't succeed to enable the 
> seafile external storage.
> I enabled the options in the config.ini, but the default storage will 
> be used. (kolab_files).

There are two possibilities:

1. Use SeaFile only.

$config['fileapi_backend']      = 'seafile';
$config['fileapi_seafile_host'] = 'localhost';

You can access only one seafile storage here. I didn't try this method with
Roundcube, it should work if you use the same user/pass as in
Roundcube/Kolab.

2. Use Kolab as main storage (and authentication/configuration source) and
"mount" Seafile storage(s) as folder(s).

$config['fileapi_backend'] = 'kolab';
$config['fileapi_drivers'] = array('seafile');

'fileapi_sources' is not required. At any time user should be able to
"mount" SeaFile storage as a folder.

Do not forget about other seafile-related config e.g.
fileapi_seafile_debug, which you can find in sample config file in git.

If (in the 2. case) you define any fileapi_sources every user should see
them on folders list.

If you find errors in connection to seafile in error log, use
$config['fileapi_seafile_ssl_verify_host'] = false;
$config['fileapi_seafile_ssl_verify_peer'] = false;

--
Aleksander Machniak
Software Developer
Kolab Systems AG: http://kolabsys.com
PGP: 19359DC1
_______________________________________________
users mailing list
users at lists.kolab.org
https://lists.kolab.org/mailman/listinfo/users