Establishment and management of file structure like git without adding the files to repositories



  • Two large file repositories need to be synchronized, each can update data (deleting, adding files), how will git be used correctly for this purpose (is there any size repositories from this storage facility?) Are there other policy options for this task?



  • How do I know you need to synchronize in both the veins? I'll try to name a couple of ready products that can be delivered and built.

    I think "on the surface" is a solution based on a solution. https://syncthing.net/ ♪ This thing is capable of "highing" the big directories, working on the basis of the hen, and until there's a situation that the same file changed on two ends, it's supposed to work perfectly well.

    The second candidate, from the choices, I'd call https://www.seafile.com/en/home/ ♪ He's good at big volumes, too, and he can only get a diff file online if he changes it.

    I'd suggest we use the rsync, but I don't understand how to start a scheme in which synchronization will take place on both sides. And most importantly, how to make sure that scheme doesn't stop, there's gonna have to be two rsync's.

    Perhaps my answer is not complete, and someone will add something else - in another reply or in commentaries.

    You' a success!


Log in to reply
 

Suggested Topics

  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2