Changes between Version 5 and Version 6 of DeveloperGuidelines/PrePopulate

Timestamp:

06/14/12 14:36:35 (13 years ago)

Author:

Fran Boon

Comment:

--

DeveloperGuidelines/PrePopulate

@@ -13 +13 @@
 == Methods ==
 === On First Run ===
-In models/000_config.py {{{deployment_settings.base.prepopulate}}} is used to control prepopulate. This is a list of directory names and will import data from a number of CSV files. The directories must be in the private/templates directory tree and must include a file called tasks.cfg.
+The template selected in models/000_config.py will be examined to see if it conains a config.py. If it does then that file's {{{settings.base.prepopulate}}} is used to control prepopulate, unless overridden in models/000_config.py.
 
-The prepopulate deployment setting can also be a number which will relate to a single directory, the numerical value is still supported because existing instances of Eden and their maintenance scripts use this number. The use of a number is discouraged in favour of the list of names because this new approach is clearer and more flexible.
+The setting is a list of directory names and will import data from a number of CSV files. The directories must be in the private/templates directory tree and must include a file called tasks.cfg.
+
+The prepopulate deployment setting can also be a number which will relate to a single directory defined in folders.cfg....the number is easier to manage in deployment shell scripts.
 
 ==== Deployment setting examples ====