revert command edit

linode · Sep 30, 2024 · 6eef6e1 · 6eef6e1
1 parent 343efd2
commit 6eef6e1
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 18 deletions.
diff --git a/...latform/migrate-to-linode/migrate-from-aws-s3-to-linode-object-storage/index.md b/...latform/migrate-to-linode/migrate-from-aws-s3-to-linode-object-storage/index.md
@@ -189,12 +189,7 @@ Rclone generally performs better when placed closer to the source data being cop
     If using Architecture 2, also include the `--bind ::0` flag to write data from your Compute Instance to your Object Storage bucket using IPv6:
 
     ```command
-    rclone copy aws:{{< placeholder "aws-bucket-name" >}}/ linode:{{< placeholder "linode-bucket-name" >}}/ \
-    --transfers 50 \
-    --rc --rc-addr=0.0.0.0:5572 \
-    --log-file=rclone.log --log-level=ERROR \
-    --rc-web-gui \
-    --rc-user {{< placeholder "USERNAME" >}} --rc-pass {{< placeholder "PASSWORD" >}}
+    rclone copy aws:{{< placeholder "aws-bucket-name" >}}/ linode:{{< placeholder "linode-bucket-name" >}}/ --transfers 50 --rc --rc-addr=0.0.0.0:5572 --log-file=rclone.log --log-level=ERROR --rc-web-gui --rc-user {{< placeholder "USERNAME" >}} --rc-pass {{< placeholder "PASSWORD" >}}
     ```
 
 #### Rclone Copy Command Breakdown

diff --git a/...ate-to-linode/migrate-from-azure-blob-storage-to-linode-object-storage/index.md b/...ate-to-linode/migrate-from-azure-blob-storage-to-linode-object-storage/index.md
@@ -185,12 +185,7 @@ Rclone generally performs better when placed closer to the source data being cop
     If using Architecture 2, also include the `--bind ::0` flag to write data from your Compute Instance to your Object Storage bucket using IPv6:
 
     ```command
-    rclone copy azure:{{< placeholder "azure-container-name" >}}/ linode:{{< placeholder "linode-bucket-name" >}}/ \
-    --transfers 50 \
-    --rc --rc-addr=0.0.0.0:5572 \
-    --log-file=rclone.log --log-level=ERROR \
-    --rc-web-gui \
-    --rc-user {{< placeholder "USERNAME" >}} --rc-pass {{< placeholder "PASSWORD" >}}
+    rclone copy azure:{{< placeholder "azure-container-name" >}}/ linode:{{< placeholder "linode-bucket-name" >}}/ --transfers 50 --rc --rc-addr=0.0.0.0:5572 --log-file=rclone.log --log-level=ERROR --rc-web-gui --rc-user {{< placeholder "USERNAME" >}} --rc-pass {{< placeholder "PASSWORD" >}}
     ```
 
 #### Rclone Copy Command Breakdown

diff --git a/...e-to-linode/migrate-from-google-cloud-storage-to-linode-object-storage/index.md b/...e-to-linode/migrate-from-google-cloud-storage-to-linode-object-storage/index.md
@@ -191,12 +191,7 @@ Rclone generally performs better when placed closer to the source data being cop
     If using Architecture 2, also include the `--bind ::0` flag to write data from your Compute Instance to your Object Storage bucket using IPv6:
 
     ```command
-    rclone copy gcs:{{< placeholder "gcs-bucket-name" >}}/ linode:{{< placeholder "linode-bucket-name" >}}/ \
-    --transfers 50 \
-    --rc --rc-addr=0.0.0.0:5572 \
-    --log-file=rclone.log --log-level=ERROR \
-    --rc-web-gui \
-    --rc-user {{< placeholder "USERNAME" >}} --rc-pass {{< placeholder "PASSWORD" >}}
+    rclone copy gcs:{{< placeholder "gcs-bucket-name" >}}/ linode:{{< placeholder "linode-bucket-name" >}}/ --transfers 50 --rc --rc-addr=0.0.0.0:5572 --log-file=rclone.log --log-level=ERROR --rc-web-gui --rc-user {{< placeholder "USERNAME" >}} --rc-pass {{< placeholder "PASSWORD" >}}
     ```
 
 #### Rclone Copy Command Breakdown