From 5abbb97fbe36c1af61ff5fb684e290a5aea607dd Mon Sep 17 00:00:00 2001 From: Cody Baker <51133164+CodyCBakerPhD@users.noreply.github.com> Date: Sat, 28 Sep 2024 21:33:03 -0400 Subject: [PATCH] shorten code blocks --- docs/user_guide/docker_demo.rst | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/docs/user_guide/docker_demo.rst b/docs/user_guide/docker_demo.rst index a943cfa58..ddf255070 100644 --- a/docs/user_guide/docker_demo.rst +++ b/docs/user_guide/docker_demo.rst @@ -102,7 +102,11 @@ It relies on some of the GIN data from the main testing suite, see :ref:`example .. code:: - docker run -t --volume /home/user/demo_neuroconv_docker:/demo_neuroconv_docker ghcr.io/catalystneuro/neuroconv:latest neuroconv /demo_neuroconv_docker/demo_neuroconv_docker_yaml.yml --output-folder-path /demo_neuroconv_docker/demo_output + docker run -t \ + --volume /home/user/demo_neuroconv_docker:/demo_neuroconv_docker \ + ghcr.io/catalystneuro/neuroconv:latest \ + neuroconv /demo_neuroconv_docker/demo_neuroconv_docker_yaml.yml \ + --output-folder-path /demo_neuroconv_docker/demo_output Voilà! If everything occurred successfully, you should see... @@ -142,6 +146,10 @@ Then, you can use the following command to run the Rclone Docker image: .. code:: - docker run -t --volume destination_folder:destination_folder -e RCLONE_CONFIG="$RCLONE_CONFIG" -e RCLONE_COMMAND="$RCLONE_COMMAND" ghcr.io/catalystneuro/rclone_with_config:latest + docker run -t \ + --volume destination_folder:destination_folder \ + -e RCLONE_CONFIG="$RCLONE_CONFIG" \ + -e RCLONE_COMMAND="$RCLONE_COMMAND" \ + ghcr.io/catalystneuro/rclone_with_config:latest This image is particularly designed for convenience with AWS Batch (EC2) tools that rely heavily on atomic Docker operations. Alternative AWS approaches would have relied on transferring the Rclone configuration file to the EC2 instances using separate transfer protocols or dependent steps, both of which add complexity to the workflow.