4 ms·

This seems way more complicated than the options the author offers in the first 80% of the article. If you consider your time valuable, just use those services

• crcastle 16y ago
  It is a bit complicated, but I think the author's writing style may make it sound more complicated than it is. Yes, it'll take a little time upfront to get it going, but this, to me, seems like a solution that would require very little monitoring/tweaking/maintenance after it's been setup.
  • gab007 16y ago
    I agree, plus if you take the time to get this working, the only limit is your server (assigned) space for file storage. I hope there will be a follow-up with step-by step info, I am interested.
  • simcop2387 16y ago
    Yes I use a similar one using unison on my laptop myself. Once setup the only time I ever have to do anything special is when there's a conflict since it won't destroy a file that I've altered on both sides before a sync has happened. This happens rarely (usually to a configuration file for some software I've put in the directory for syncing) and is the behavior that I want, e.g. don't destroy local changes automatically let me decide what to do about it so that there's no unintentional data loss. And while there is a conflict it will continue to happily sync everything else happily ignoring the conflicts. Edit: I should also say that I'm not using lsyncd or anything like that to manage it, just cron on the laptop. I initiate it one way at a regular time. Though using lsycnd does sound interesting. I also didn't use autossh and instead opted for OpenVPN since I knew I was going to want the other benefits of having a VPN at the time (being able to tunnel traffic easily for the most part)