maintainer: eGroupWare evelopers
eGroupware now includes a WebDAV client VFS implementation, so if you set your file repository to be "http ://some.webdav.url.com" in the setup app, and set the file repository type to DAV all vfs-using apps should transparently access their files over webdav.
The key benefit of this is that then you can access your file repository directly using WebDAV enabled applications. In Windows (with IE 5+?), you can create a web-folder, and point it at your WebDAV server. On Linux you can mount it as a file system using davfs. OpenOffice?, MSOffice, and plenty of other major applications can save files directly to a WebDAV share.
The easiest way to get a DAV repository going is to use the Apache web server - either Apache 1.x with the mod_dav module, or Apache 2 (which has DAV builtin) - once you have mod_dav installed correctly RTFM, you should easily be able to get an (unauthenticated) WebDAV server going.
The WebDAV repository's "document root" requires the same kind of file structure and permissions as is required for the standard VFS_SQL file repository - ie there needs to be a directory named "/home", and this need to be writable by Apache.
This is the tricky bit : ideally you want user names and passwords for the DAV server, so not just any fool can read your data. Although authentication is "optional" for VFS_DAV- its essential from a security standpoint if you want to make your files accessible over the internet.
Of course, you can manually create and manage .htaccess and htpasswd files for each user. But ideally you want to be able to log into the WebDAV repository using the same username and password as you use with egroupware.
To do this, you need to get Apache to authenticate against whatever you have setup eGroupware to store its accounts information in. For instance, if you authenticate against a PostgreSQL database you would install mod_auth_pg
http://authpg.sourceforge.net/mod_auth_pg.html (there is an example config for mod_auth_pg in CVS : for LDAP use mod_auth_ldap http://httpd.apache.org/docs-2.0/mod/mod_auth_ldap.html, and so on (there are actually Apache modules that will authenticate against almost anything - Ideally we would figure out a way to authenticate against eGroupware itself)
(Anyone who figures out how to use one of these other authentication modules, please add the info here)
back to: eGroupWare / DeveloperDocs / (VFS)?