This update fixes a couple of logic errors where synchronising content in a child folder of a Folder set to not synchronise would be ignored in one direction but not the other, resulting in inconsistent content between the Repository and File System.
Also in this version we enforced that if setting a new Document or Folder base type for content create on the Repository that the Type actually exists in the Repository first and that it's of the correct type. This also affects the setting of mimeMappings to Document Types where you can override these defaults and define a specific Document Type to be used during content creation based on the MIME type of the file being synchronised.
This will be the last release of the 0.1.x branch.
This version is now available as a downloadable zip file <strong>edrive-1.0.3-bin.zip</strong> that can be unzipped to a directory on your machine and run directly from the <strong>/bin</strong> folder using either the <strong>edrive.bat</strong> for windows or the <strong>edrive.sh</strong> for Linux and Mac OSX
The <strong>/config</strong> directory contains an initial empty <em><strong>eDrive.json</strong></em> file as well as an <em><strong>eDrive.json.example</strong></em> file that can be used for reference when setting up your own Synchronisers. There is also a default <em><strong>eDrive.pass</strong></em> file containing a pass phrase used for encrypting the passwords.
Some points of note for this release:
1. <strong>eDrive</strong> now serialises the <em>snapshot states</em> of each configured Synchroniser when shutting down so that the next start up remembers it's previous state. 2. If a configured Synchroniser references a Repository that is not available when <strong>eDrive</strong> starts up it will attempt to re-establish a connection every 5 minutes rather than just disabling the Synchroniser. 3. We added a new <em>shutdown command</em> so that clients can shutdown <strong>eDrive</strong> cleanly.
<strong>A Call to arms…</strong>
We would like to elicit more involvement from the Open Source community to help build native interfaces for <strong>eDrive</strong> on ALL the common OS platforms. We are thinking along the lines of a <em><strong>tortoies svn</strong></em> like plugin for Windows Explorer, Mac OSX and Nautilus.
Anybody interested in getting involved can leave a comment here OR head over to the SourceForge site and raise a ticket or start a discussion.
We are building a REST based Web Service client for <strong>eDrive</strong> that we will Open Source when ready to Beta.
It should be pretty easy to build light weight native clients as the only connections to <strong>eDrive</strong> is via 2 sockets, no programming language restriction as there are no libraries required…
