#5 Bidirectional synchronisation

已關閉
achilleas4 年之前創建 · 4 條評論

I see a few options here.

  1. Have an upload script (which we already do) and a separate download script that does gin download --content so it pulls everything.
  2. Have separate download and get-content scripts. One pulls the changes from the server, the other downloads all the annexed content.
  3. Have a single sync script that runs gin sync --content to do upload, download, full content synchronisation, and also resolves conflicts.
I see a few options here. 1. Have an upload script (which we already do) and a separate download script that does `gin download --content` so it pulls everything. 2. Have separate `download` and `get-content` scripts. One pulls the changes from the server, the other downloads all the annexed content. 3. Have a single `sync` script that runs `gin sync --content` to do upload, download, full content synchronisation, and also resolves conflicts.
julien colomb 評論 4 年之前'
所有者

we went for: one script only:

gin sync gin uplaod

  • hashed gin download --content write a log file if error, keep window open and write a message
we went for: one script only: gin sync gin uplaod + hashed gin download --content write a log file if error, keep window open and write a message
julien colomb 評論 4 年之前'
所有者

seems there is "only bash working" ? Can you write some info in the readme file about what script is doing what, and maybe move old ones into a different folder?

seems there is "only bash working" ? Can you write some info in the readme file about what script is doing what, and maybe move old ones into a different folder?

I have a .bat version of the error checking which I haven't pushed because I haven't had the chance to test it. I'll push it now and add a note in the README.

I have a .bat version of the error checking which I haven't pushed because I haven't had the chance to test it. I'll push it now and add a note in the README.

Let me know if you're happy with the current state and the descriptions in the README and feel free to close this issue if there's nothing more to be done for this.

Let me know if you're happy with the current state and the descriptions in the README and feel free to close this issue if there's nothing more to be done for this.
jcolomb4 年之前 關閉
登入 才能加入這對話。
未選擇里程碑
未指派成員
2 參與者
正在加載...
取消
保存
尚未有任何內容