The Hubzilla
|
Public Member Functions | |
init () | |
post () | |
get () | |
activate ($pdo, $channel) | |
Public Member Functions inherited from Zotlabs\Web\Controller | |
init () | |
post () | |
get () | |
Zotlabs\Module\Cdav::activate | ( | $pdo, | |
$channel | |||
) |
Referenced by Zotlabs\Module\Cdav\get(), and Zotlabs\Module\Cdav\init().
Zotlabs\Module\Cdav::get | ( | ) |
Zotlabs\Module\Cdav::init | ( | ) |
This server combines both CardDAV and CalDAV functionality into a single server. It is assumed that the server runs at the root of a HTTP domain (be that a domainname-based vhost or a specific TCP port.
This example also assumes that you're using SQLite and the database has already been setup (along with the database tables).
You may choose to use MySQL instead, just change the PDO connection statement.
UTC or GMT is easy to work with, and usually recommended for any application.
Make sure this setting is turned on and reflect the root url for your WebDAV server.
This can be for example the root / or a complete path to your server script.
Database
The backends. Yes we do really need all of them.
This allows any developer to subclass just any of them and hook into their own backend systems.
The directory tree
Basically this is an array which contains the 'top-level' directories in the WebDAV server.
Zotlabs\Module\Cdav::post | ( | ) |