Sync - Revision history

Wizzup: /* Radicale Testing Server */

2024-04-27T10:09:25Z

Radicale Testing Server

← Older revision		Revision as of 10:09, 27 April 2024
Line 178:		Line 178:
	=== Radicale Testing Server ===		=== Radicale Testing Server ===

	For testing purposes, here is how to quickly run a radicale server, this ~~assumed it's~~ installed.		For testing purposes, here is how to quickly run a radicale server, this assumes that radicale is installed.

	<pre>		<pre>

Wizzup: Add instructions on how to sync to additional calendars

2024-04-27T09:06:22Z

Add instructions on how to sync to additional calendars

@@ Line 134: / Line 134: @@
 </pre>
-==== Warning: TLS Chain validation issues ====
+This means that is no specific database is provided above, the synchronisation will be done against this calendar. If you have a need to have multiple remote calendars and sync them against other Maemo calendars, create a new calendar using the Calendar application (Settings -> Edit calendars -> New). For the sake of the example, call it MoreTasks.
 If you run into problems with TLS Chain validation, first try to figure out if the problem is on your end.

Wizzup: Update tls chain validation issues to mention it's ok now on chimaera

2024-04-22T22:57:11Z

Update tls chain validation issues to mention it's ok now on chimaera

← Older revision		Revision as of 22:57, 22 April 2024
Line 138:		Line 138:
	==== Warning: TLS Chain validation issues ====		==== Warning: TLS Chain validation issues ====

	If you run into problems with TLS Chain validation, first try to figure out if the problem is on your end. Syncevolution did have a problem for me validation the chain of my next cloud instance, so for testing purposes I set '''SSLVerifyServer = 0''' in '''/home/user/.config/syncevolution/nextcloud/peers/target-config/config.ini'''		If you run into problems with TLS Chain validation, first try to figure out if the problem is on your end.
			Syncevolution did have a problem for me validation the chain of my next cloud instance, so for testing purposes I set '''SSLVerifyServer = 0''' in '''/home/user/.config/syncevolution/nextcloud/peers/target-config/config.ini'''

			On Chimaera this problem should no longer exist - it was only a problem for Beowulf.

	== Radicale synchronising ==		== Radicale synchronising ==

Wizzup at 10:44, 10 October 2022

2022-10-10T10:44:45Z

← Older revision		Revision as of 10:44, 10 October 2022
Line 18:		Line 18:

	== Synchronizing with syncevolution CalDav + CardDav ==		== Synchronizing with syncevolution CalDav + CardDav ==

			First, install syncevolution using '''sudo apt-get install syncevolution'''.

	If you get stuck in an odd state setting this up, you could consider running the following to get to a clean state, at least with regards to syncevolution configuration:		If you get stuck in an odd state setting this up, you could consider running the following to get to a clean state, at least with regards to syncevolution configuration:

Wizzup: /* NextCloud synchronizing */

2022-10-10T10:39:21Z

NextCloud synchronizing

← Older revision		Revision as of 10:39, 10 October 2022
Line 79:		Line 79:
	backend=carddav \		backend=carddav \
	target-config@nextcloud contacts		target-config@nextcloud contacts



	syncevolution --configure \		syncevolution --configure \

Wizzup at 10:38, 10 October 2022

2022-10-10T10:38:58Z

← Older revision		Revision as of 10:38, 10 October 2022
Line 173:		Line 173:
	* Synchronizing calendar to radicale gives errors if there are unnamed calendar events.		* Synchronizing calendar to radicale gives errors if there are unnamed calendar events.
	* Synchronizing contacts to radicale gives errors if there are contacts without Firstname or Lastname.		* Synchronizing contacts to radicale gives errors if there are contacts without Firstname or Lastname.

			= Further reading =

			The "old" Maemo page on synchronisation might prove fruitful for those wanting to port over more: https://wiki.maemo.org/Sync

Wizzup: /* Files synchronization */

2022-10-10T10:37:48Z

Files synchronization

← Older revision		Revision as of 10:37, 10 October 2022
Line 164:		Line 164:
	= Files synchronization =		= Files synchronization =

	~~TODO~~		This section ought to discuss software that can be used for this purpose, e.g. syncthing, nextcloud, ...


			Parazyd started on a GUI for nextcloud file synchronisation, here: https://github.com/maemo-leste-extras/nextcloud-sync

	= Known Issues =		= Known Issues =

Wizzup at 10:29, 10 October 2022

2022-10-10T10:29:32Z

← Older revision		Revision as of 10:29, 10 October 2022
Line 7:		Line 7:
	== GUI ==		== GUI ==

			The "Syncevolution Frontend" application is a graphical interface to syncevolution. While the interface can technically help you set up the synchronisation configuration through the graphical interface, we haven't tried it and do not have instructions for it at the moment. We only use it for scheduling and running synchronisations - the configuration still has to be done using the console, currently.

			(Contributions welcome)

	<gallery widths=320px heights=173px>		<gallery widths=320px heights=173px>

Wizzup at 10:26, 10 October 2022

2022-10-10T10:26:56Z

← Older revision		Revision as of 10:26, 10 October 2022
Line 4:		Line 4:

	Synchronizing calendar, notes and tasks (using CalDav) and contacts (using CardDav) can be done using syncevolution (other [https://syncevolution.org/documentation/backends/ backends are available], but not currently documented here). A frontend to running synchronization tasks is available in the repository (Syncevolution Frontend).		Synchronizing calendar, notes and tasks (using CalDav) and contacts (using CardDav) can be done using syncevolution (other [https://syncevolution.org/documentation/backends/ backends are available], but not currently documented here). A frontend to running synchronization tasks is available in the repository (Syncevolution Frontend).

			== GUI ==


			<gallery widths=320px heights=173px>
			File:syncevolution.png\|main syncevolution screen
			File:syncevolution-2.png\|syncevolution for a specific sync target
			</gallery>


	== Synchronizing with syncevolution CalDav + CardDav ==		== Synchronizing with syncevolution CalDav + CardDav ==

BuZz at 00:34, 10 October 2022

2022-10-10T00:34:59Z

← Older revision		Revision as of 00:34, 10 October 2022
Line 1:		Line 1:
	~~= Synchronization =~~

	This page explains and suggests various ways of synchronizing contacts, calendars and files.		This page explains and suggests various ways of synchronizing contacts, calendars and files.

	== Calendar, Notes, Tasks and Contacts ==		= Calendar, Notes, Tasks and Contacts =

	Synchronizing calendar, notes and tasks (using CalDav) and contacts (using CardDav) can be done using syncevolution (other [https://syncevolution.org/documentation/backends/ backends are available], but not currently documented here). A frontend to running synchronization tasks is available in the repository (Syncevolution Frontend).		Synchronizing calendar, notes and tasks (using CalDav) and contacts (using CardDav) can be done using syncevolution (other [https://syncevolution.org/documentation/backends/ backends are available], but not currently documented here). A frontend to running synchronization tasks is available in the repository (Syncevolution Frontend).

	=== Synchronizing with syncevolution CalDav + CardDav ===		== Synchronizing with syncevolution CalDav + CardDav ==

	If you get stuck in an odd state setting this up, you could consider running the following to get to a clean state, at least with regards to syncevolution configuration:		If you get stuck in an odd state setting this up, you could consider running the following to get to a clean state, at least with regards to syncevolution configuration:
Line 15:		Line 13:
	</pre>		</pre>

	==== NextCloud synchronizing ====		=== NextCloud synchronizing ===

	We will be synchronizing the calendar and such using local '''maemo-events''', '''maemo-notes''' and '''maemo-tasks''' backends using the '''caldav''' backend.		We will be synchronizing the calendar and such using local '''maemo-events''', '''maemo-notes''' and '''maemo-tasks''' backends using the '''caldav''' backend.
Line 126:		Line 124:


	===== Warning: TLS Chain validation issues =====		==== Warning: TLS Chain validation issues ====

	If you run into problems with TLS Chain validation, first try to figure out if the problem is on your end. Syncevolution did have a problem for me validation the chain of my next cloud instance, so for testing purposes I set '''SSLVerifyServer = 0''' in '''/home/user/.config/syncevolution/nextcloud/peers/target-config/config.ini'''		If you run into problems with TLS Chain validation, first try to figure out if the problem is on your end. Syncevolution did have a problem for me validation the chain of my next cloud instance, so for testing purposes I set '''SSLVerifyServer = 0''' in '''/home/user/.config/syncevolution/nextcloud/peers/target-config/config.ini'''

	=== Radicale synchronising ===		== Radicale synchronising ==

	Radicale is a simple CardDAV and CalDAV server, and is set up similarly to nextcloud. Just browse to the Radicale web URL, and use the following URLs:		Radicale is a simple CardDAV and CalDAV server, and is set up similarly to nextcloud. Just browse to the Radicale web URL, and use the following URLs:
Line 140:		Line 138:
	The username (and optional password) are the radicale credentials.		The username (and optional password) are the radicale credentials.

	==== Radicale Testing Server ====		=== Radicale Testing Server ===

	For testing purposes, here is how to quickly run a radicale server, this assumed it's installed.		For testing purposes, here is how to quickly run a radicale server, this assumed it's installed.
Line 152:		Line 150:
	Now browse to http://localhost:5223, create an account (password is optional), and you should be able to synchronize, assuming the devices can reach your radicale server (don't have it listen on localhost only, perhaps use 0.0.0.0:5223 for LAN testing)		Now browse to http://localhost:5223, create an account (password is optional), and you should be able to synchronize, assuming the devices can reach your radicale server (don't have it listen on localhost only, perhaps use 0.0.0.0:5223 for LAN testing)

	== Files synchronization ==		= Files synchronization =

	TODO		TODO

	== Known Issues ==		= Known Issues =

	* Synchronizing calendar to radicale gives errors if there are unnamed calendar events.		* Synchronizing calendar to radicale gives errors if there are unnamed calendar events.
	* Synchronizing contacts to radicale gives errors if there are contacts without Firstname or Lastname.		* Synchronizing contacts to radicale gives errors if there are contacts without Firstname or Lastname.