# HG changeset patch
# User galaxyp
# Date 1454095651 18000
# Node ID 5bf19713c281881baeeb49f280e512c821250612
# Parent  7e078d4e40f810b7f6d41d40df6142441f681a5f
planemo upload for repository https://github.com/galaxyproteomics/tools-galaxyp/tools/bumbershoot/customProDB commit 141369f97aa2804d2bbfd9ed620ea2a5574994c2-dirty

diff -r 7e078d4e40f8 -r 5bf19713c281 tool-data/customProDB.loc.sample
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/tool-data/customProDB.loc.sample	Fri Jan 29 14:27:31 2016 -0500
@@ -0,0 +1,18 @@
+#This file lists the locations and dbkeys of all the fasta files
+#under the "genome" directory (a directory that contains a directory
+#for each build). The script extract_fasta.py will generate the file
+#all_fasta.loc. This file has the format (white space characters are
+#TAB characters):
+#
+#<unique_build_id>	<dbkey>		<display_name>	<file_path>
+#
+#So, all_fasta.loc could look something like this:
+#
+#apiMel3	apiMel3	Honeybee (Apis mellifera): apiMel3		/path/to/genome/apiMel3/apiMel3.fa
+#hg19canon	hg19		Human (Homo sapiens): hg19 Canonical		/path/to/genome/hg19/hg19canon.fa
+#hg19full	hg19		Human (Homo sapiens): hg19 Full			/path/to/genome/hg19/hg19full.fa
+#
+#Your all_fasta.loc file should contain an entry for each individual
+#fasta file. So there will be multiple fasta files for each build,
+#such as with hg19 above.
+#
diff -r 7e078d4e40f8 -r 5bf19713c281 tool_data_table_conf.xml.sample
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/tool_data_table_conf.xml.sample	Fri Jan 29 14:27:31 2016 -0500
@@ -0,0 +1,7 @@
+<tables>
+    <!-- Locations of all customProDB annotations under genome directory -->
+    <table name="customProDB" comment_char="#">
+        <columns>value, dbkey, name, path</columns>
+        <file path="tool-data/customProDB.loc" />
+    </table>
+</tables>