110 feature sync

[dketterer]

How to test with the server:

Create a playground: bob playground
Changes in bob.yml:

project: localhost:8100/00000000-0000-0000-0000-000000000000/playground

Replace sync: {} with

sync:
  testing:
    path: second-level
    version: feature1

Start the server bob run run-debug-server and copy the debugtoken from stdout.

Update or init auth context: bob auth update --token=<debugtoken> && bob auth switch default

Run some commands

bob build
cd ../playground
./../bob/run sync ls
./../bob/run sync ls-remote --insecure
./../bob/run sync push --insecure
# change something locally in ./second-level
./../bob/run sync pull --insecure

[dketterer]

@Equanox I think client and server are at a point where you can take another look.
What is working:

• ls
• ls-remote
• push
• pull
• keeping a cache of file hashes locally so repeated pushs and pulls are cheap

What is missing:

• user guidance
• handling of (empty) directories
• conflicting collection paths
• easy selection of remote collections to pull without manual editing of bob.yaml

[dketterer]

Known issue:
Directory sync has some bugs, I tried to use the hash of the dir name but somehow server and client calculcate different hashes. Dirs are always resynced with bob sync.

Missing feature:
Automatic editing of the bob.yaml after running bob sync create. Instead the yaml part is display and the user can add it manually.