Hello Arelor!

 >> OK.. so it appears that it created the encrypted directories
 >> because I configured it to do that.  Had I stipulated that
 >> mycrypt: NOT encrypt the directories, using mycrypt:/arn/
 >> archive would have placed the encrypted files in the actual
 >> /arn/archive location?
 >>

 A> I don't understand the question.

Sorry.. it *was* a rather long-winded statement.  What I mean  
is that I configured the mycrypt: remote to encrypt directories  
*and* files.

.: perhaps that is why I don't see any encrpyted files in the  
existing /arn/archive directory.  Instead, there is a new  
encrypted directory in the root, and an encrpyted subdir inside  
of that one, and *then* the encrypted files are in the latter.

So.. my guess is that if I modify mycrypt: to only encrypt the  
files, and NOT the dirs, *then* a copy using to "rclone copy  
[files] mycrypt:/arn/archive" will park the files into the  
readable /arn/archive directory?


 A> "mycrypt:" uses any path you set for it. It might be
 A> test1:, test1:/folder or whatever. If you use test1:/
 A> horse_pictures then anything you upload to it (ie. rclone
 A> copy horse.jpg mycrypt will be placed, in encrypted form,
 A> under test1:/horse_pictures/.

It seems that the Windows version doesn't really use the  
configured directory.  Firstly, what I use at the command line  
overrides what's in the config.  I like the fact that it  
automatically creates missing directories.

If I use "rclone copy [files] mycrypt:" ..without any directory  
parameter after mycrypt:, the files get stored at the root  
level of my webhost account.

-- 
  ../|ug

--- OpenXP 5.0.57
 * Origin:  (618:500/23.10)