This is a CalDAV and CardDAV adapter for EteSync
This is a CalDAV and CardDAV adapter for EteSync
This package provides a local CalDAV and CardDAV server that acts as an EteSync compatibility layer (adapter). It's meant for letting desktop CalDAV and CardDAV clients such as Thunderbird, Outlook and Apple Contacts connect with EteSync.
If all you want is to access your data from a computer, you are probably better off using the web app.
The easiest way to start using etesync-dav is by getting one of the pre-built binaries from the releases page.
These binaries are self-contained and can be run as-is, though they do not start automatically on boot. You'd need to either start them manually, or set up autostart based on your OS.
For Linux users there's a short installation guide in the wiki.
etesync-davand open the management UI in your browser: http://localhost:37358/
For advanced usage and CLI instructions please refer to the advanced usage section.
Please note that some antivirus/internet security software may block the CalDAV/CardDAV service from running - make sure that etesync-dav is whitelisted.
Don't forget to set up EteSync to automatically start on startup. Instructions for this are unfortunately OS dependent and out of scope for this README.
You now need to set up your CalDAV/CardDAV client using your username and the password you got in the previous step.
Depending on the client you use, the server path should either be:
On most clients this should automatically detect your collections (i.e. calendars and address books).
If your client does not automatically detect your collections, you will need to manually add them. You can find the links in the management UI when you click on your username.
http://localhost:37358/for both servers, your EteSync username as the username and the DAV password you got in configuration and running as the password.
Note: if you enabled SSL in etesync-dav, you should follow the TbSync instructions for self-signed certificates.
Using TbSync is recommended, because it includes address book support (Lightning does not), automatically discovers all your calendars/address books/tasks, and just works better in general. However, you can also do the following:
File > New Calendar > On the Network > CalDavfor calendars and tasks, or
New Address Book > Remote > CardDavin Cardbook for address books
GNOME Calendar and Contacts do not support adding WebDAV calendars and address books directly, but you can add them in Evolution and they will appear correctly in all the apps.
http://localhost:37358/as the server.
While EteSync-DAV works great on Windows 10, due to bugs in Windows itself, the instructions require a few extra steps for syncing with Outlook, Windows Calendar and Windows people. Other clients, such as Thunderbird, do no require these extra steps.
Please take a look at the Windows 10 instructions for more information.
While EteSync-DAV works great on macOS, due to bugs in macOS Mojave, the instructions require a few extra steps for syncing with Contacts.app and Calendar.app. Other clients, such as Thunderbird, do no require these extra steps.
Please take a look at the macOS instructions for more information.
By default, iOS only syncs events 30 days old and newer, which may look as if events are not showing. To fix this, got to: Settings -> Calendar -> Sync and change to the wanted time duration.
Or better yet, just use the EteSync iOS client.
It's probably easiet to just follow these instructions for setting up autostart. Alternatively, you can try following the instructions below.
Make sure you have
/usr/lib/systemd/user/etesync-dav.serviceon your system (should be there when installing from your distro's package manager), and then, to start the service:
systemctl --user start etesync-davTo enable auto-start on boot:
systemctl --user enable etesync-dav
Make sure you installed
etesync-dav.appby dragging it to your
Applicationsdirectory through finder. Enable autostart by for example following these instructions.
Follow these instructions.
This methods are not as easy as the pre-built binaries method above, but are also simple. Please follow the instructions below, following which follow the instructions in the Configuration and running section below.
Run one time initial setup to persist the required configuration into a docker volume. Check out the configuration section below for more information.
docker run -it --rm -v etesync-dav:/data etesync/etesync-dav manage add USERNAME
Run etesync-dav in a background docker container with configuration from previous step. This wil (re)start the container on boot and after crashes.
docker run --name etesync-dav -d -v etesync-dav:/data -p 37358:37358 --restart=always etesync/etesync-dav
After this, refer to the Setting up clients section below and start using it!
To update to the latest version of the docker image, run:
docker pull etesync/etesync-dav
etesync-davis available on AUR.
Install virtual env (for Python 3) from your package manager, for example:
The bellow commands will install etesync to a directory called
venvin the local path. To install to a different location, just choose a different path in the commands below.
Set up the virtual env:
virtualenv -p python3 venv source venv/bin/activate pip install etesync-dav
Run the etesync commands as explained in the Configuration and running section:
./venv/bin/etesync-dav manage ... ./venv/bin/etesync-dav ...
Please note that you'll have to run
source venv/bin/activateevery time you'd like to run the EteSync commands.
cd /path/to/file(most likely
etesync-davfor ease of use, by e.g:
mv linux-etesync-dav etesync-dav
chmod +x etesync-dav
You need to first add an EteSync user using
./etesync-dav manage, for example:
./etesync-dav manage add USERNAME
USERNAMEwith the username you use with your EteSync account or self-hosted server.
and then run the server:
Note: if you are using this with the legacy etesync server you should also pass
If you are self-hosting the EteSync server, just enter your server URL when adding your account. Alternatively, you can set the default URL to be used by setting the
ETESYNC_URLenvironment variable to the URL of your server when running etesync-dav. By default it uses the official EteSync server at
EteSync-DAV should automatically use the system's proxy settings if set correctly. Alternatively, you can set the
HTTPS_PROXYenvironment variables to manually set the proxy settings.
If the etesync backend server is using self signed certs, the DAV bridge may refuse to connect. To solve this, run the following commands prior to starting the DAV bridge.
Alternatively, if the security of certificate is not an issue (say the server is on a private network and not publicly accessible), you can ignore the certificate completely with the following commands prior to starting the DAV bridge.
export CURL_CA_BUNDLE=''; export REQUESTS_CA_BUNDLE='';
In order to put
etesync-davin debug mode so it print extra debug information please pass it the
-Dflag like so:
While this works on Linux, BSD and macOS, the Windows pre-compiled binary is compiled in "no console" mode, which means it can't print to the terminal. In order to get the debug information on Windows, please redirect the output log to file, like so:
set ETESYNC_LOGFILE=output.log etesync-dav.exe -D
etesync-davstores data in the directory specified by the
ETESYNC_DATA_DIRenvironment variable. This includes a database and the credentials cache.
ETESYNC_DATA_DIRdefaults to a subdirectory of the appropriate data directory for your platform. For example: 1.
~/.local/share/etesync-davon Linux. 2.
~/Library/Application Support/etesync-davon macOS 3.
C:\Documents and Settings\\Application Data\Local Settings\etesync\etesync-davon Windows (most likely).
See the appdirs module docs for mor examples.
This depends on the Radicale server for operation.