use odrive to connect storage bucket to a windows environment with online sync
instead of the files as fcloud make them URLs with the file name and icon associated
make the folders as directories
add the ability to connect this storage space that syncs to webdav server (with files being downloaded from links via the GCP)so the files can mapped to a network drive
ignoring my 3rd grade writing skills is there a way to do this see attached image
Hi @nhutwelker,
You can’t really properly share out an odrive created/controlled folder structure in this way because of the missing context. odrive folders require odrive context to make proper use of them. You can try to facilitate it by making sure everything is always synced and there are no placeholders, but it is the placeholders that can throw a wrench in the works. I believe your request for replacing placeholders with folders and URLs is a suggestion to try to get around this, but that will not be possible.
Based on your diagram, it sounds like you are really just looking for a way to backup data from your Windows file servers to cloud storage. If you are wanting to be able to make use of both sides (cloud storage and windows networked mounts) at the same time, where some users make use of the cloud storage, and some users to make use of the “old school” windows networked file servers (SMB mounts), while keeping those two endpoints in sync with each other, it may be theoretically possible to do with odrive. You still run up against the concern of placeholder files, but it is a bit more manageable. See attached crappy doodle below:
Basically you install odrive onto the file server(s) (or a machine connected to the file servers), use “sync to odrive” to map the data folders to remote cloud storage locations for sync (https://docs.odrive.com/docs/manage-sync#section-sync-external-folders), and then use the odrive client on the user’s machines that will be accessing the cloud storage instead of the legacy network shares.
Now, this all being said, this type of use case it really outside the “expected” or “designed” use cases for odrive, currently. odrive is really intended to be a consumer cloud storage sync solution. In the above scenario you are, instead, using the odrive client as a behind-the-scenes bridge for syncing a very large, multi-user data repository with cloud storage. In this type of scenario things like rate of change, scale of data, number of users, etc can have a large impact on how effective the solution would be.
My gut is telling me that odrive is probably not the right solution for this intermediate, bulk-processing bridge, currently.
There are things we are working on to try to directly facilitate these use cases as part of a more business-oriented product, but they are not available yet.
