Comments for digital playground http://www.digitalplayground.at Unternehmenshomepage Digitalplayground Mon, 25 Jul 2011 15:00:32 +0000 hourly 1 http://wordpress.org/?v=3.3.1 Comment on Another Dropbox alternative – somewhat by Thomas Brandstetter http://www.digitalplayground.at/?p=1#comment-310 Thomas Brandstetter Mon, 25 Jul 2011 15:00:32 +0000 http://www.digitalplayground.at/?p=1#comment-310 I haven't encountered this problem yet and I never had any conflicts during my sync. Actually I'm testing the Unison backend for Sparkleshare because this is closer to my needs as my actual configuration. If you like to test it too, you can find it under: https://github.com/lgordon/SparkleShare Cheers Thomas I haven’t encountered this problem yet and I never had any conflicts during my sync. Actually I’m testing the Unison backend for Sparkleshare because this is closer to my needs as my actual configuration. If you like to test it too, you can find it under:

https://github.com/lgordon/SparkleShare

Cheers

Thomas

]]> Comment on Another Dropbox alternative – somewhat by Niobos http://www.digitalplayground.at/?p=1#comment-309 Niobos Mon, 25 Jul 2011 14:37:07 +0000 http://www.digitalplayground.at/?p=1#comment-309 First of all: wow. You describe exactly what I'm looking for! And yes, there's a "but" as well: I'd like to have some sort of notification when there is a conflict. However, I don't see any activity in the log-file when this is the case... The stdout of the unison process reports the conflict, but nothing is written to the log-file (and hence displayed by growl). Have you encountered this as well? Any solutions? I'm thinking of running fsmonitor.py myself, and dispatching unison from my scripts, so I can catch the exit code, but that would imply that unison would have to re-scan the entire root. (I'm assuming that unison uses the output of fsmonitor.py somehow in it's scan). thx, Niobos First of all: wow. You describe exactly what I’m looking for!

And yes, there’s a “but” as well: I’d like to have some sort of notification when there is a conflict. However, I don’t see any activity in the log-file when this is the case… The stdout of the unison process reports the conflict, but nothing is written to the log-file (and hence displayed by growl). Have you encountered this as well? Any solutions?

I’m thinking of running fsmonitor.py myself, and dispatching unison from my scripts, so I can catch the exit code, but that would imply that unison would have to re-scan the entire root. (I’m assuming that unison uses the output of fsmonitor.py somehow in it’s scan).

thx,
Niobos

]]> Comment on Another Dropbox alternative – somewhat by Real time file synchronization like Dropbox via Unison http://www.digitalplayground.at/?p=1#comment-274 Real time file synchronization like Dropbox via Unison Tue, 19 Jul 2011 00:09:14 +0000 http://www.digitalplayground.at/?p=1#comment-274 [...] stumbled upon this post that outlines a solution based on the bleeding edge version of Unison, which includes the [...] [...] stumbled upon this post that outlines a solution based on the bleeding edge version of Unison, which includes the [...]

]]> Comment on Another Dropbox alternative – somewhat by admin http://www.digitalplayground.at/?p=1#comment-60 admin Sun, 29 May 2011 17:03:14 +0000 http://www.digitalplayground.at/?p=1#comment-60 Sorry, that I've deleted the comments. I just wanted to delete the SPAM posts and unfortunately hit the approved posts too. Sorry, that I’ve deleted the comments. I just wanted to delete the SPAM posts and unfortunately hit the approved posts too.

]]>