jgaunt/rclone
1
0
Fork 0
mirror of https://github.com/rclone/rclone.git synced 2026-01-05 10:03:17 +00:00
Code Issues Projects Releases Wiki Activity

docs: promote the use of -i/--interactive and "rclone sync -i" everywhere #1574

Browse Source
This commit is contained in:
Nick Craig-Wood
2020-06-05 17:04:23 +01:00
parent a3b3e1f646
commit 844b903595
27 changed files with 55 additions and 43 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
docs/content/docs.md
View File

@@ -83,7 +83,7 @@ rclone uses a system of subcommands. For example
rclone ls remote:path # lists a remote
rclone copy /local/path remote:path # copies /local/path to the remote
rclone sync /local/path remote:path # syncs /local/path to the remote
rclone sync -i /local/path remote:path # syncs /local/path to the remote
The main rclone commands with most used first
@@ -249,11 +249,11 @@ file or directory like this then use the full path starting with a
So to sync a directory called `sync:me` to a remote called `remote:` use
rclone sync ./sync:me remote:path
rclone sync -i ./sync:me remote:path
or
rclone sync /full/path/to/sync:me remote:path
rclone sync -i /full/path/to/sync:me remote:path
Server Side Copy
----------------
@@ -286,8 +286,8 @@ same.
This can be used when scripting to make aged backups efficiently, eg
rclone sync remote:current-backup remote:previous-backup
rclone sync /path/to/files remote:current-backup
rclone sync -i remote:current-backup remote:previous-backup
rclone sync -i /path/to/files remote:current-backup
Options
-------
@@ -329,7 +329,7 @@ directory must not overlap the destination directory.
For example
rclone sync /path/to/local remote:current --backup-dir remote:old
rclone sync -i /path/to/local remote:current --backup-dir remote:old
will sync `/path/to/local` to `remote:current`, but for any files
which would have been updated or deleted will be stored in
@@ -604,7 +604,7 @@ Add an HTTP header for all download transactions. The flag can be repeated to
add multiple headers.
```
rclone sync s3:test/src ~/dst --header-download "X-Amz-Meta-Test: Foo" --header-download "X-Amz-Meta-Test2: Bar"
rclone sync -i s3:test/src ~/dst --header-download "X-Amz-Meta-Test: Foo" --header-download "X-Amz-Meta-Test2: Bar"
```
See the GitHub issue [here](https://github.com/rclone/rclone/issues/59) for
@@ -616,7 +616,7 @@ Add an HTTP header for all upload transactions. The flag can be repeated to add
multiple headers.
```
rclone sync ~/src s3:test/dst --header-upload "Content-Disposition: attachment; filename='cool.html'" --header-upload "X-Amz-Meta-Test: FooBar"
rclone sync -i ~/src s3:test/dst --header-upload "Content-Disposition: attachment; filename='cool.html'" --header-upload "X-Amz-Meta-Test: FooBar"
```
See the GitHub issue [here](https://github.com/rclone/rclone/issues/59) for
@@ -1197,7 +1197,7 @@ or with `--backup-dir`. See `--backup-dir` for more info.
For example
rclone sync /path/to/local/file remote:current --suffix .bak
rclone sync -i /path/to/local/file remote:current --suffix .bak
will sync `/path/to/local` to `remote:current`, but for any files
which would have been updated or deleted have .bak added.