
Stockage en ligne
Get flash to fully experience Pearltrees
Executive summary dvcs-autosync is a project to create an open source replacement for Dropbox/Wuala/Box.net/etc. based on distributed version control systems (DVCS). It offers nearly instantaneous mutual updates when a file is added or changed on one side but with the added benefit of (local, distributed) versioning and that it does not rely on a centralized service provider, but can be used with any DVCS hosting option including a completely separate server - your data remains your own . Synchronization of directories is based on DVCS repositories. Git is used for main development and is being tested most thoroughly as the backend storage, but other DVCS such as Mercurial are also supported. dvcs-autosync is comparable to SparkleShare in terms of overall aim, but takes a more minimalistic approach. A single Python script monitors the configured directory for live changes, commits these changes to the DVCS (such as git) and synchronizes with other instances using XMPP messages.
DVCS-Autosync: A personal Dropbox replacement based on Git | Rene Mayrhofer's virtual home
BBOX - The cloud under your (version) control, as easy and drag 'n drop.
You are in control of your Cloud. Because BBox is based on Subversion technology, so you install the server, you choose the settings. You choose whether to encrypt the main storage hard drive or not. If using a Secure protocol like HTTPS or not. Just work(s) What if your files are shared to your team, seamlessly?Unison File Synchronizer
UPDATE #4 It’s 2012, and this project is still alive, although I haven’t worked on lipsync as much as I should. I want to, and have new ideas to implement and try out in the next few months. The two way sharing is a bit hacky, and I don’t like it, the installer creates a cronjob : that checks for server changes to sync back every minute – and it tries to avoid conflicts by not running if a sync the other way is happening . Yes, if you’re using 2 computers at once it could get confused, but so far, it’s pretty good – but something I want to improve. I’m also very interested in ownCloud and using remote storage auth protocol like Unhosted proposes – these are two things I’d love to integrate into lipsync over the next few months. I really think having something that is all owned by the user, and in full control of the user, is still the ultimate way.

