From a2895c2dac682efbb1191f10cef2fa9318dc3c6d Mon Sep 17 00:00:00 2001 From: "mike@2d6d71f56ce2a992244350475251df87c26fe351" Date: Thu, 12 Sep 2024 15:40:24 +0000 Subject: [PATCH] Added a comment --- ...t_4_dc8884bf9f6bd6bdac73f26fad417355._comment | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 doc/special_remotes/rclone/comment_4_dc8884bf9f6bd6bdac73f26fad417355._comment diff --git a/doc/special_remotes/rclone/comment_4_dc8884bf9f6bd6bdac73f26fad417355._comment b/doc/special_remotes/rclone/comment_4_dc8884bf9f6bd6bdac73f26fad417355._comment new file mode 100644 index 0000000000..66a9df0119 --- /dev/null +++ b/doc/special_remotes/rclone/comment_4_dc8884bf9f6bd6bdac73f26fad417355._comment @@ -0,0 +1,16 @@ +[[!comment format=mdwn + username="mike@2d6d71f56ce2a992244350475251df87c26fe351" + nickname="mike" + avatar="http://cdn.libravatar.org/avatar/183fa439752e2f0c6f39ede658d81050" + subject="comment 4" + date="2024-09-12T15:40:24Z" + content=""" +Here are a few pointers for switching from `git-annex-remote-rclone` (old helper program) to `rclone gitannex` (rclone's builtin support): + +0. Figure out `rcloneprefix` (directory relative to the rclone remote (rclone term here)) and `rclonelayout` (layout of the git-annex content therein). If you set it up just like in `git-annex-remote-rclone`'s README, those are `git-annex` and `lower`. +1. Update rclone and git-annex +2. Rename the old remote, `git remote rename my_rclone_remote my_rclone_remote.old; git annex renameremote my_rclone_remote my_rclone_remote.old` +3. Create a new remote, copying the encryption settings: `git annex initremote my_rclone_remote --sameas=my_rclone_remote.old type=rclone rcloneremotename=my_rclone_remote rcloneprefix=git-annex rclonelayout=lower` + +It might be possible to just change the type of the remote but at the time I'm writing this, that didn't work so I renamed the old remote and created a new one, with `--sameas` to not lose any encryption settings. +"""]] -- 2.30.2