Open steven-johnson opened 9 years ago
One part of implementing this will be a naming/addressing model. One option for this would be (continuing the Unix-y approach) the notion of mounting a shared folder into your local Drive hierarchy (and then accessing it regularly.)
OTOH this might be a bit too much of a stretch, and e.g. weird for it to not show up in the Drive web interface, etc.
Another option might be a way to associate a name (e.g. "halide" with a shared folder) and be able to access it via paths like /shared/halide/... . Then at least hopefully the /shared part would make users less likely to expect to see it in the web interface.
Seems reasonable. Probably want to make the name configurable so it wouldn't mean that an actual subfolder named "shared" becomes inaccessible.
Has there been any updates on this? I'm trying to download data from a collaborator who uses google drive onto my unix servers and I can't find a good solution.
I'd like to use skicka to pull down nightly builds of Halide, which are in a world-readable folder, but skicka (apparently) doesn't provide a way to access things outside of Your Very Own Drive Folder.