RClone
| User availability .MU. | |
| This is a multi-user application. Can be installed by any user in the RClone Access group. | |
Install Location | |
MergerFS mount | /home/${username}/rclone/gmedia/ |
Google Drive | /home/${username}/rclone/gdrive/ |
RClone cache | /home/${username}/rclone/cache/ |
Config Location | /home/${username}/.config/rclone/ |
Nginx Location | N/A |
Service Location | |
MergerFS | /etc/systemd/system/home-${username}-rclone-gmedia.mount |
RClone | /etc/systemd/system/[email protected]${username}.service |
Port | N/A |
Here is a list of questions and answers surrounding RClone which don’t need an article for each question, but it is worth having a centralized place for them. Enjoy!
Yes, you can view the move.log file. Simply go to the directory /home/username/rclone/ and you’ll see the file there. You can use nano to view it in a terminal. So the command for that would be nano /home/username/rclone/move.log
There is a script that is ran on a cron job at 2am every morning. This will initiate the uploading process.
Best practice says to use the GMedia folder for everything located at /home/username/rclone/gmedia. Sonarr, Plex, Ombi etc. This is a combination of what is stored locally, and what is on Google Drive.
For other clients there maybe a graphical interface you can use, however, with our implementation of RClone there is only the command line interface (CLI)
You can use the following command after doing sudo su - on your server to elevate your permissions properly. Where you see username, please enter in your actual username.
qb rclone upload username
This is to avoid any API bans from Google themselves. This is a common issue when constantly uploading data to Google Drive and they implement limits. Whilst you can edit the script to increase or even remove this limit, we do not recommend it as it will cause issues.
For more information on editing the script, please see here.
