Update canto_deploy.yaml - better commenting on how to define where the...

Update canto_deploy.yaml - better commenting on how to define where the internal SQL database lives (under Model::TrackModel:)

canto_deploy.yaml

@@ -15,12 +15,18 @@ annotation_figure_field: 0
 # disable deletion buttons on genotype management page?
 show_quick_deletion_buttons: 0
 
+# this will define Canto's internal SQL database (track.sqlite3 and files for all curation sessions) to the the 'data' sub-folder of 'canto-space' (/data/export/canto-space/data), which is where all data should reside.
+# Here filepaths are relative. Have an initial '/' in '/data/track.sqlite3' and '/data' below, otherwise track.sqlite3 and the data will appear in '/data/export/canto-space/canto/data' rather than in '/data/export/canto-space/data'.
 Model::TrackModel:
   connect_info:
-# filepath plus track.sqlite3
+# this sets the path (and name) of the sqlite3 file (track.sqlite3), which queries curation sessions within canto
+# make sure it does include the initial '/', otherwise curation session will be misplaced in '/data/export/canto-space/canto/data' 
+# Make sure the folder where the SQL database 'track.sqlite3' lives (/data in /data/track.sqlite3) matches the data_directory value (/data) 
     - dbi:SQLite:dbname=/data/track.sqlite3
   schema_class: Canto::TrackDB
-# filepath 
+# this sets the path to the 'data' sub-folder of 'canto-space', which is where all curation data should reside.
+# make sure it does include the initial '/', otherwise curation session will be misplaced in '/data/export/canto-space/canto/data' 
+# and make sure the folder where the SQL database 'track.sqlite3' lives (/data/track.sqlite3) matches the data_directory value (/data)
 data_directory: /data
 
 #Database to connect to - 'connect_info:' bit is the only part that needs changes on a weekly basis