I have a little problem as I'm kind of new doing this, I have rclone up and running and created a remote but somehow in cannot manage to mount any folder from my remote (Putio) to a local directory (created before).
Could someone spare some time showing me the proper procedure, I've read and typed command lines presented on put.io website as well as on rclone.org but nothing seems to work.
Thanks in advance
What is your rclone version (output from rclone version)
Which OS you are using and how many bits (eg Windows 7, 64 bit)
OSX Catalina 10.15.1
Which cloud storage system are you using? (eg Google Drive)
The command you were trying to run (eg rclone copy /tmp remote:tmp)
rclone mount remote:path/to/files /path/to/local/mount --daemon
A log from the command with the -vv flag (eg output from rclone -vv copy /tmp remote:tmp)
Failed to create file system for "remote:path/to/files": didn't find section in config file
Hello, I realized I should have put the right command and not just copypaste the example, here is the exact command
rclone mount cloudmovies:/Movies/ /Macintosh HD/users/myname/putio-local/Movies/mount --daemon
And here is what I get
rclone mount remote:path /path/to/mountpoint [flags]
I'm not sure if the paths from the remote directory and/or the local are right, here is the rclone config
e) Edit existing remote
n) New remote
d) Delete remote
r) Rename remote
c) Copy remote
s) Set configuration password
q) Quit config
Choose a number from below, or type in an existing value
1 > cloudmovies
A mount can make cloud-files accessible for any application - as they just think it's a normal harddrive or network location. So yes - you can use Plex. It is a common usecase here.
Applications reading from a mount is easy and will work out of the box on a mount.
If you want applications to write data too, this may require using --vfs-cache-mode writes as this is required for compatibility with more complex writing operations that the OS and applications would normally expect a normal hard-drive to be able to perform.
Just be aware that there are some technical caveats to running Plex from a cloud-drive instead of a local disk. it can work fine - but some Plex settings (like most of the extended metadata scanning) ought to be disabled from running automatically. A lot of these need to actually read parts of each file for the analysis, and some of them will even read the whole file. That's not a great idea to do often/automatically on a large collection over the internet.
This megathread contains a lot of rclone/Plex combo information you may find useful, however do note that not everything will be applicable to you as this is a in-depth guide for a spesific and more advanced setup That Animosity uses. I would focus on the details regarding how to config Plex:
I think you will probably also find this flag useful for your use-case: --track-renames
It makes it so that you won't have to re-upload everything just because you moved some directories around or gave new names to files. Instead it will just move/rename them on the server and save you most of the work.