X-Git-Url: https://git.arvados.org/arvados.git/blobdiff_plain/3fb3557b13cce8fee3bab0f81ab03b78fbef67dd..a66dcf3c878be422520771e5bde3791248dba001:/doc/user/tutorials/tutorial-firstscript.html.textile.liquid diff --git a/doc/user/tutorials/tutorial-firstscript.html.textile.liquid b/doc/user/tutorials/tutorial-firstscript.html.textile.liquid index 5d0a4daa3c..245e89066b 100644 --- a/doc/user/tutorials/tutorial-firstscript.html.textile.liquid +++ b/doc/user/tutorials/tutorial-firstscript.html.textile.liquid @@ -22,7 +22,7 @@ First, you should do some basic configuration for git (you only need to do this ~$ git config --global user.email you@example.com -On the Arvados Workbench, navigate to "Compute %(rarr)→% Code repositories":http://{{site.arvados_workbench_host}}/repositiories . You should see a repository with your user name listed in the *name* column. Next to *name* is the column *push_url*. Copy the *push_url* value associated with your repository. This should look like git@git.{{ site.arvados_api_host }}:you.git. +On the Arvados Workbench, navigate to "Compute %(rarr)→% Code repositories":http://{{site.arvados_workbench_host}}/repositories . You should see a repository with your user name listed in the *name* column. Next to *name* is the column *push_url*. Copy the *push_url* value associated with your repository. This should look like git@git.{{ site.arvados_api_host }}:you.git. Next, on the Arvados virtual machine, clone your git repository: @@ -98,7 +98,8 @@ h2. Create a pipeline template Next, create a file that contains the pipeline definition: -
$ cat >the_pipeline <<EOF
+
~/you/crunch_scripts$ cd ~
+~$ cat >the_pipeline <<EOF
 {
   "name":"My first pipeline",
   "components":{
@@ -110,7 +111,7 @@ Next, create a file that contains the pipeline definition:
           "dataclass": "Collection"
         }
       },
-      "script_version":"you:master"
+      "script_version":"you:master"
     }
   }
 }
@@ -120,18 +121,18 @@ EOF
 
 * @cat@ is a standard Unix utility that simply copies standard input to standard output
 * @<the_job@ redirects standard output to a file called @the_job@
+* @>the_pipeline@ redirects standard output to a file called @the_pipeline@
 * @"name"@ is a human-readable name for the pipeline
 * @"components"@ is a set of scripts that make up the pipeline
 * The component is listed with a human-readable name (@"do_hash"@ in this example)
 * @"script"@ specifies the name of the script to run.  The script is searched for in the "crunch_scripts/" subdirectory of the @git@ checkout specified by @"script_version"@.
-* @"script_version"@ specifies the version of the script that you wish to run.  This can be in the form of an explicit @git@ revision hash, or in the form "repository:branch" (in which case it will take the HEAD of the specified branch).  Arvados logs the script version that was used in the run, enabling you to go back and re-run any past job with the guarantee that the exact same code will be used as was used in the previous run.  You can access a list of available @git@ repositories on the Arvados workbench under "Compute %(rarr)→% Code repositories":http://{{site.arvados_workbench_host}}/repositiories .
+* @"script_version"@ specifies the version of the script that you wish to run.  This can be in the form of an explicit @git@ revision hash, or in the form "repository:branch" (in which case it will take the HEAD of the specified branch).  Arvados logs the script version that was used in the run, enabling you to go back and re-run any past job with the guarantee that the exact same code will be used as was used in the previous run.  You can access a list of available @git@ repositories on the Arvados workbench under "Compute %(rarr)→% Code repositories":http://{{site.arvados_workbench_host}}//repositories .
 * @"script_parameters"@ describes the parameters for the script.  In this example, there is one parameter called @input@ which is @required@ and is a @Collection@.
 
 Now, use @arv pipeline_template create@ tell Arvados about your pipeline template:
 
 
-
$ arv pipeline_template create --pipeline-template "$(cat the_pipeline)"
+
~$ arv pipeline_template create --pipeline-template "$(cat the_pipeline)"