Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
O
openbis
Manage
Activity
Members
Labels
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
sispub
openbis
Commits
d3a97ad6
Commit
d3a97ad6
authored
7 years ago
by
kohleman
Browse files
Options
Downloads
Patches
Plain Diff
Minor, config adaption: added data set based destination folders
SVN: 38949
parent
3b617d29
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
deep_sequencing_unit/tracking/dist/etc/service.properties
+3
-2
3 additions, 2 deletions
deep_sequencing_unit/tracking/dist/etc/service.properties
with
3 additions
and
2 deletions
deep_sequencing_unit/tracking/dist/etc/service.properties
+
3
−
2
View file @
d3a97ad6
...
@@ -41,10 +41,11 @@ debug = true
...
@@ -41,10 +41,11 @@ debug = true
old-data-set-backlog-number
=
1000
old-data-set-backlog-number
=
1000
# List of DataSet Types which should be copied into an extra folder
# List of DataSet Types which should be copied into an extra folder
dataset-type-list
=
FASTQ_GZ
dataset-type-list
=
FASTQ_GZ
, FASTQC
# folder where the data should be copied to
# folder where the data should be copied to
destination-folder
=
/tmp/
FASTQ_GZ-destination-folder
=
/Users/kohleman/dest/fastq_gz
FASTQC-destination-folder
=
/Users/kohleman/dest/fastqc
# rsync binary
# rsync binary
rsync-binary
=
/opt/local/bin/rsync
rsync-binary
=
/opt/local/bin/rsync
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment