Local rclone remote location

What is the problem you are having with rclone?

I am not able to choose the location of local remote. On Windows it seems to get created under the folder that has the rclone.exe.

What is your rclone version (output from rclone version)

rclone-v1.56.0-windows-amd64

Which cloud storage system are you using? (eg Google Drive)

local

The command you were trying to run (eg rclone copy /tmp remote:tmp)

reclone config

The rclone config contents with secrets removed.

[dropbox]
type = dropbox
token = {"access_token":"","token_type":"bearer","refresh_token":"","expiry":""}

[gdrive]
type = drive
scope = drive
token = {"access_token":""}
team_drive = 

[encrypted]
type = crypt
remote = dropbox:/Encrypted
password = 
password2 = 

[local-remote]
type = local
nounc = true

It is handled similar to regular filesystem paths: Relative paths resolve to current directory, absolute paths to root of current drive.

You need to create an alias to get a local remote rooted at a specific path.

Thanks for the reply.
So I tried it out and it seems like it has one way syncing. So I basically created a file in the mounted remote and it didn't appear in the local folder until I unmounted and re-mounted.
However when I created the file in the local folder while the remote was mounted, the new file appeared in the mounted remote.
This is how I am accessing the local remote (on Windows 10)
./rclone.exe mount --vfs-cache-mode full local-remote: X:

And this is my new config file

[dropbox]
type = dropbox
token = {""}

[gdrive]
type = drive
scope = drive
token = {""}
team_drive = 

[encrypted]
type = crypt
remote = dropbox:/Encrypted
password = 
password2 = 

[local-remote]
type = alias
remote = D:\local-remote

Dropbox isn't a polling remote so you have to wait 5 minutes for the default dir-cache time to expire.

I am trying to mount my local-remote not the dropbox one.

The local remote is not polling so you have to wait for the cache time to expire…

Is there a way to force polling on local remotes? Otherwise they would be unreliable and useless.

You can lower the dir cache time.

You can run the remote control daemon and run a refresh command.

I’d do the first.

Polling is not yet implemented on local filesystems.
Waiting for core team to get over their backlogs or external go developers to volunteer their time :slight_smile:

I just want to double check. Is it at least reliable where my data would be correctly preserved when I unmount?

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.