csync cli usage
The ownCloud csync version uses the same syntax as the original csync but with a differing url syntax/module.
1. create a folder/repository through the web interface that you will sync to
2. choose a local folder to sync to owncloud
3. sync with the following syntax:
- Code: Select all
csync <local_folder> ownclouds://user:firstname.lastname@example.org/owncloud/files/webdav.php/<remote_folder>
4. enter login credentials when requested, if not supplied in step 3 above
[ note to do: does anyone know how to provide credentials on the cli when the password includes non-std characters eg. @ and ! ? ]
csync cli usage is very useful when you need to automate syncing to ownCloud from the CLI. I've experienced some unusual behaviour though. On one occasion, syncing a local folder to a newly created ownCloud folder resulted in the local files being removed rather than synced to the oc folder.
In this case, you may want to use the --dry-run switch the first time to check what changes will be made.
The current mirall/csync combination uses time stamps ( correct? ) to determine if a file needs to be synced. This is called conflict resolution. See the [url]original csync documentation here[/url]. Currently this is done on a timer of 30 seconds ( correct? ). Mirall has had a timer config option added in the last release which allows this timer to be changed eg. sync check every 5 minutes instead of 30 seconds ).
[note to do: does anyone know the timer config value and in which file this is changed? ]
The mirall client under Linux now has the ability to use a filesystem notification mechanism such as inotify, to decide on sync changes. This is enabled using the -DINOTIFY switch when compiling mirall.
[note to do: does anyone know how and where the timer value is disabled and inotify option enabled? ]