implemented config for pimutils. TODO: list of programs needed is starting to become large. For example, this commit introduces the reqirement of a pass password store. make some documentation.
This commit is contained in:
parent
baa1ff01ce
commit
a9a3a93a7d
5 changed files with 134 additions and 0 deletions
58
vdirsyncer/.config/vdirsyncer/config
Normal file
58
vdirsyncer/.config/vdirsyncer/config
Normal file
|
@ -0,0 +1,58 @@
|
|||
# An example configuration for vdirsyncer.
|
||||
#
|
||||
# Move it to ~/.vdirsyncer/config or ~/.config/vdirsyncer/config and edit it.
|
||||
# Run `vdirsyncer --help` for CLI usage.
|
||||
#
|
||||
# Optional parameters are commented out.
|
||||
# This file doesn't document all available parameters, see
|
||||
# http://vdirsyncer.pimutils.org/ for the rest of them.
|
||||
[general]
|
||||
# A folder where vdirsyncer can store some metadata about each pair.
|
||||
status_path = "~/.cache/vdirsyncer/status/"
|
||||
# CARDDAV
|
||||
[pair nextcloud_contacts]
|
||||
# A `[pair <name>]` block defines two storages `a` and `b` that should be
|
||||
# synchronized. The definition of these storages follows in `[storage <name>]`
|
||||
# blocks. This is similar to accounts in OfflineIMAP.
|
||||
a = "nextcloud_contacts_local"
|
||||
b = "nextcloud_contacts_remote"
|
||||
# Synchronize all collections that can be found.
|
||||
# You need to run `vdirsyncer discover` if new calendars/addressbooks are added
|
||||
# on the server.
|
||||
collections = ["from a", "from b"]
|
||||
# Synchronize the "display name" property into a local file (~/.contacts/displayname).
|
||||
metadata = ["displayname"]
|
||||
# To resolve a conflict the following values are possible:
|
||||
# `null` - abort when collisions occur (default)
|
||||
# `"a wins"` - assume a's items to be more up-to-date
|
||||
# `"b wins"` - assume b's items to be more up-to-date
|
||||
conflict_resolution = "b wins"
|
||||
[storage nextcloud_contacts_local]
|
||||
# A storage references actual data on a remote server or on the local disk.
|
||||
# Similar to repositories in OfflineIMAP.
|
||||
type = "filesystem"
|
||||
path = "~/.contacts/"
|
||||
fileext = ".vcf"
|
||||
[storage nextcloud_contacts_remote]
|
||||
type = "carddav"
|
||||
url = "https://nextcloud.gabevenberg.com"
|
||||
username = "Toric"
|
||||
# The password can also be fetched from the system password storage, netrc or a
|
||||
# custom command. See http://vdirsyncer.pimutils.org/en/stable/keyring.html
|
||||
password.fetch = ["command", "pass", "nextcloud.gabevenberg.com/Toric"]
|
||||
# CALDAV
|
||||
[pair nextcloud_calendar]
|
||||
a = "nextcloud_calendar_local"
|
||||
b = "nextcloud_calendar_remote"
|
||||
collections = ["from a", "from b"]
|
||||
# Calendars also have a color property
|
||||
metadata = ["displayname", "color"]
|
||||
[storage nextcloud_calendar_local]
|
||||
type = "filesystem"
|
||||
path = "~/.calendars/"
|
||||
fileext = ".ics"
|
||||
[storage nextcloud_calendar_remote]
|
||||
type = "caldav"
|
||||
url = "https://nextcloud.gabevenberg.com/"
|
||||
username = "Toric"
|
||||
password.fetch = ["command", "pass", "nextcloud.gabevenberg.com/Toric"]
|
Loading…
Add table
Add a link
Reference in a new issue