You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now we need to use log docker commands, it would be great if these were simpler.
Perhaps you could create a script so the user could just list their token, the relative path and filename of the manifest, the relative path for where the directory containing the samples and the relative path for the outputs. At this point, I just look up a previous upload or download and edit those three things...nothing else changes.
Right now we need to use log docker commands, it would be great if these were simpler.
Perhaps you could create a script so the user could just list their token, the relative path and filename of the manifest, the relative path for where the directory containing the samples and the relative path for the outputs. At this point, I just look up a previous upload or download and edit those three things...nothing else changes.
So, go from this:
docker run --rm -it -e ACCESS_TOKEN=<mytokenhere> -e REDWOOD_ENDPOINT=ucsc-cgp.org -v $(pwd)/myDirectory/myManifest.tsv:/dcc/manifest.tsv -v $(pwd)/myDirectory:/samples -v $(pwd)/myDirectory/outputs:/outputs quay.io/ucsc_cgl/core-client:1.1.0 spinnaker-upload --force-upload --skip-submit /dcc/manifest.tsv
to:
$ rwUpload myToken myDirectory/myManifest.tsv myDirectory myDirectory/outputs
The text was updated successfully, but these errors were encountered: