You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

2.0 KiB

Table of Contents

  1. Demo
  2. About
  3. Package Contents
  4. Issues


Demo

IMAGE ALT TEXT


About

Sync files across directories.

alt text

Package Contents

Path Comment
doc Diagrams.
src.com.olexyn.ensync.artifacts Data Model: Maps, Directories, Files.
src.com.olexyn.ensync.shell .sh files to ease interaction with the host.
src.com.olexyn.ensync.ui JavaFX.
src.com.olexyn.ensync.Execute Issue .sh commands.
src.com.olexyn.ensync.Main Run from here.
src.com.olexyn.ensync.Flow Flow of the synchronization.
src.com.olexyn.ensync. Low level helper methods.


Issues

  • Add tests.
  • Remove Map entries, once file ops is performed.
  • Reduce disk access.
  • Add error handling. (i.e. if a web-directory is not available)
  • Track files that were modified during the loop.
    • currently writeStateFile just takes from find
    • this means any changes made during the loop will be written to the StateFile
    • and created files are tracked by comparing StateFile (=old state) and State (=new state).
    • because of this it will appear as if the file created while the loop was running was already there.
    • thus the creation of said file will not be replicated to the other directories.
    • to solve this writeStateFile should take the old State and manually add every operation that was performed by the loop (!= user created file while the loop was running).
  • File is created in DirB
    • Sync creates the file in DirA
    • Sync creates the file in DirB
      • this means the file in DirB is overwritten with cp for no reason.
      • implement a check to prevent this.