Adding remote support with push and pull functionality #66
sebastianrath
started this conversation in
Ideas
Replies: 1 comment
-
Hello, I'm stay here to look, and try to get more feedback in a near futur :) . |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Abstract
The goal is to add a
push/pull
functionality to SnowFS without requiring an application on the server side. Possible services to look at are:To support
push/pull
on such "remotes", we must design the upload and download semantics of SnowFS to guarantee a data integrity under every circumstance and possible scenario.Network/Online storage and Git
There are plenty of articles online explaining how to set-up a Git repository on Dropbox, Google Drive or other shared online storages (in the following simply called ONLINE-STORAGE-SERVICE). Since Git supports pushing and pulling to other directories (used for shared network push/pull), this functionality is often misused since folders/files like in Dropbox have a local file path (e.g.
/Users/$USERNAME/Dropbox
). Although such setup might work for single users, or simply coincidentally, this will often destroy the Git repository because the synchronization of these online storages is often undefined.E.g: Once a change is made to a repository, ONLINE-STORAGE-SERVICE will sync the changes. Now, a concurrent upload/download from another user or system will result in synchronization conflicts that need to be manually resolved. Below is a list of issues often displayed by ONLINE-STORAGE-SERVICES:
Where to go from here?
There are plenty scenarios of conflicts possible, from object-files available but no refs or vice-verse, up to file-locking-issues. This discussion is a starting point to gather synchronization strategies and how to ensure the repository is always well-defined.
Additional resources:
Dropbox
Beta Was this translation helpful? Give feedback.
All reactions