astrada/google-drive-ocamlfuse — an open-source project — sits at 6.0k GitHub stars. FUSE filesystem over Google Drive
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
For other installation options, please refer to the wiki.
How to build
Requirements
OCaml >= 4.08.0
dune >= 2.0.0
fuse3 >= 3.10.0
gapi-ocaml >= 0.4.9
sqlite3-ocaml >= 1.6.1
tiny_httpd >= 0.10
otoml >= 1.0.1
ounit >= 2.0.0
Configuration and installation
To build the executable, run
dune build @install
To install it, run (as root, if your user doesn't have enough privileges)
dune install
To uninstall anything that was previously installed, execute
dune uninstall
Usage
First, you must set up OAuth
2.0:
Activate the
Google Drive API.
Create an OAuth client ID.
Choose Desktop as Application type.
Set the Name to anything you like.
This way you will get a Client ID and Client secret that you can use to
access your Drive. To authorize google-drive-ocamlfuse, pass the client ID
and the client secret on the command line, e.g.:
This command will create the default application directory
(~/.gdfuse/default), containing the configuration file config (see the
wiki
page
for more details about configuration). And it will start a web browser to
obtain authorization to access your Google Drive. This way, you can modify the
default configuration before mounting the filesystem.
Then, you can choose a local directory to mount your Google Drive (e.g.: ~/GoogleDrive).
Create the mount point, if it doesn't exists:
mkdir ~/GoogleDrive
Then, you can mount the filesystem (append & to the command, if you want to
run it in background):
Using label to distinguish different accounts. The program will use the
directory ~/.gdfuse/[label] to host the configuration, the application
state, and the file cache. No file is shared among different accounts, so you
can have a different configuration for each one.
To unmount the filesystem, issue this command:
fusermount3 -u ~/GoogleDrive
On distributions that still provide the older helper name, use
fusermount -u ~/GoogleDrive instead.
Troubleshooting
This application is still under testing, so there are probably bugs to
discover and fix. To be extra sure, if you want, you can mount the filesystem
in read-only mode, modifying the configuration (see the
documentation),
to avoid any write attempt to the server. Anyway, the rm command will simply
trash your file, so you should always be able to rollback any changes. If you
have problems, you can turn on debug logging:
google-drive-ocamlfuse -debug mountpoint
The process is always kept in foreground; -debug enables debug and verbose
logging.
In ~/.gdfuse/default you can find curl.log that will track every request
to the Google Drive API, and gdfuse.log that will log FUSE operations and
cache management. If something goes wrong, you can try clearing the cache,
with this command:
google-drive-ocamlfuse -cc
If something still doesn't work, try starting from scratch removing everything
in ~/.gdfuse/default. In this case you will need to reauthorize the
application.
Note that in order to reduce latency, cached metadata remains valid for 60
seconds by default (configurable). After it expires, the next normal resource
operation checks the server for changes. So, if you make a change to your
documents (server side), you won't see it immediately in the mounted filesystem.
Filesystem-capacity queries such as df use the latest in-memory quota snapshot
without contacting Drive; they may report stale values, or unlimited capacity
before the first snapshot is available.
Note also that Google Documents will be exported read-only.
Support
If you have questions, suggestions or want to report a problem, you may want
to open an issue
on github.
How active is development on astrada/google-drive-ocamlfuse?
The most recent commit recorded on astrada/google-drive-ocamlfuse was 2 months ago, based on the GitHub push timestamp. The repository has 366 forks — one of the better signals of community interest.
Is astrada/google-drive-ocamlfuse open source?
Yes — astrada/google-drive-ocamlfuse ships under the MIT license, which makes its source code freely readable (and, depending on license terms, forkable and reusable). Source: github.com/astrada/google-drive-ocamlfuse.
What license does astrada/google-drive-ocamlfuse use?
astrada/google-drive-ocamlfuse is released under the MIT license. Always verify the LICENSE file directly on GitHub for the authoritative terms — license strings can be edited out of sync with a project's actual stance.
What topics is astrada/google-drive-ocamlfuse associated with?
GitHub's repository topics for astrada/google-drive-ocamlfuse: "filesystem", "fuse", "google-drive", "ocaml". TopGit's editorial category is open-source.
Where can I see astrada/google-drive-ocamlfuse in action?
The project maintains a homepage at https://astrada.github.io/google-drive-ocamlfuse/. The README tab on this page also usually contains screenshots and a quickstart.
Where do I read more about astrada/google-drive-ocamlfuse?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/astrada/google-drive-ocamlfuse is the definitive source.
Read full README in the tab above.
Still deciding about google-drive-ocamlfuse?
One click hands the question to an AI along with this page — see what it says about google-drive-ocamlfuse.