Using the terminal is far from intuitive, both because of the non-trivial path of the Google Drive folder and because of the encoding of file names.įor example, to access our Test Documents.odt file shown in the screenshot above, we need to replace myemail with our email account without and 1000 with our user id, as returned by id -u: $ cd '/run/user/1000/gvfs/google-drive:host=,user=myemail'ĭrwx- 1 francesco francesco 0 0ABL_QtLrcLmOUk9PVAĭr-x- 1 francesco francesco 0 GVfsSharedWithMeġ1lfzX-8dH_eWtf2JWa3caRtodOnlXDbN: OpenDocument Text The problem with this approach is that it seems great only for GUI applications. We need to make sure we’ve enabled Files, which corresponds to Google Drive:įrom now on, we’ll find an extra entry in the file manager that corresponds to our Google Drive account: GNOME Online Accounts allows us to choose which Google services we want to integrate into the desktop. This is mainly due to the –vfs-cache-mode full option. In this way, the integration of Google Drive into the local file system is seamless both with the file manager – Nemo, in our case – and with any other application, such as LibreOffice. $ rclone mount -daemon -vfs-cache-mode full gdrive:/. In the following commands, we need to replace gdrive with the name of our remote, if different: $ mkdir mylocalfolder
If everything is correct, we can list the files and directories in our Google Drive account: $ rclone ls gdrive:įinally, we can mount Google Drive to a local folder. Avoid configuring a shared drive with n.Choose y to authenticate rclone with a browser.Leave client_id and client_secret empty unless we have our own Google API credentials.Enter the number for Google Drive, which is 18 in rclone 1.62.2.Enter a name for our remote, like gdrive.Select n for a new remote, which is a named remote storage system.We prepared a reference guide to rclone config, as its output is too verbose: Rclone v1.62.2 has successfully installed. Let’s start by installing rclone using the official script: $ sudo -v curl | sudo bash