halueda / auto-sync

automatic synchronize folders

auto-sync

automatic synchronize folders

auto-sync's Issues

use perl native cp rm mv not to depend on cygwin

Currently auto-sync is depend on Cygwin because it needs following commands:
/bin/cp
/bin/mv
/bin/rm

To replace them with perl native function/package, more applicable to the environment without cygwin.
E.g., Windows + ActivePerl environment.

Handling sharepoint WebDAV

Sharepoint WebDAV does not returns update time of a file correctly if the file is updated from application, like Excel, or Web I/F of sharepoint.

day_limit variable is passed as argument of functions

$OPTS{day_limit} can be used instead of function argument.

unnecessary backup file

If a file is continuously modified in one side, then another side backup is made everytime sync is success.
If the file is backed up in last sync, the next backup file can be omitted.

add .diff files when create .conflict

auto-sync generates .conflict file when it find conflict (both side update).
Sometimes it is difficult to make diff file of both file at the moment, if the file is contiuously modified.

if .diff file is generated when the conflict file is generated, the merge could be easier.

poor error handling about system()

Several place, system() is used but they often have poor error handling, and the other places, `` is used for appropriate error handling.

Something like mysystem() function should be defined, in which error message is hadled appropriately, e.g., output to LOG file, but easier than to use than ``.

If a file locked in one side is deleted in the other side, the locked file is undeleted in both side after sync

If a file locked in one side is deleted in the other side, the locked file is undeleted in both side after sync.

1. In one side a file is locked, e.g., opened by Excel application.
2. The file is deleted in the other side directory
3. sync tries to delete this side file but failed because it is locked
4. next sync found the file exist and misunderstood it is newly placed
5. The file is copied back to the other side, and it looks like undeleted.

Unit test should be prepared

Unit test should be prepared.
Maybe with PerlUnit.

_last.json file can be uploaded

_last.json file is internal management file only in local side directory.
Though, the _last.json file is uploaded to remote side cirectory, if

1. the local directory newly generated
2. the connection is hanged when the first sync after the generation
3. first sync is success and whole directory is copied by copy_dir() function

No document

There should be documents for:

• what this do
• how to use
• how to write configuration file

Possibly both in English and Japanese.