this question relates to using symbolic links on Linux-like platforms
I’m wondering what best practices would be for a situation where the following exists:
The need to have a single save folder from the application’s perspective
To use two cloud hosts (say dropbox / google drive)
To have this single folder synched to both cloud locations with odrive.
–This first part I think is easy (but correct me if I’m wrong). Because Odrive creates separate directory trees for each hosting account with the fork beginning in the “odrive” directly You would simply create a symlink (I’m on a Mac) from one or the other of the directories over to the mirror in the other provider tree. For example link the directory /User/whatever/odrive/Google Drive/Billy/fooMIRROR to the /User/whatever/odrive/Dropbox/bill/fooMIRROR . This way, from the Apllications perspective you would be saving in one folder but getting dual uploads happening.
NOW ILL MUDDY THE WATER - (and for clarity: I realize that each hosting service has its own way of doing version control and I haven’t settled on my choices yet, but for this thread let’s stuck with those solutions that allow a “make this version current” so to speak. As opposed to, say Google Drive that does give a version history, but requires you to download the older version manual. I’m not interested in that—and in this context the answer would be self-evident (just overwrite the local file)z
Here’s where I think I need help. When implementing versioning on one or the other platforms. if I roll back a version on one of the platforms will that translate back to the host computer, and thus, through the symlink, cause a change to be pushed out to the other host storage platform.
Just wondering. If there is a better solution to using “dual-homed, mirrored” storage with version control with odrive. That’s really what I’m looking for here.
thanks in advance!