#5 Bidirectional synchronisation

Suljettu
4 vuotta sitten avasi achilleas · 4 kommenttia

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 kommentoitu 4 vuotta sitten
Omistaja

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 kommentoitu 4 vuotta sitten
Omistaja

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?
Achilleas Koutsou kommentoitu 4 vuotta sitten
Omistaja

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.
Achilleas Koutsou kommentoitu 4 vuotta sitten
Omistaja

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.
Kirjaudu sisään osallistuaksesi tähän keskusteluun.
Ei merkkipaalua
Ei osoitettua
2 osallistujaa
Ladataan...
Peruuta
Tallenna
Sisältöä ei vielä ole.