Changes between Version 50 and Version 51 of Doc/gLite/TemplateCustomization

Timestamp:

Jun 21, 2007, 4:52:05 PM (18 years ago)

Author:

/C=FR/O=CNRS/OU=UMR8607/CN=Michel Jouvin/emailAddress=jouvin@…

Comment:

--

Doc/gLite/TemplateCustomization

@@ -6 +6 @@
 Site customization to QWGtemplates is done through a small set of templates used to define variables used as input by QWG templates. This doesn't cover OS basic configurationt that is decribed in the page about [wiki:Doc/TemplateCustom template framework].
 
-All site parameters related to QWG middleware are supposed to be declared in template `pro_lcg2_config_site.tpl`. To start a new site, import the site paramater template [source:templates/trunk/sites/example/site/pro_lcg2_config_site.tpl example]. The list of all available variables with their description and their default value can be consulted in template source:templates/trunk/grid/glite-3.0.0/defaults/site.tpl. '''This template is a critical part of standard templates and should not be modified or duplicated'''. 
+All site parameters related to QWG middleware are supposed to be declared in template `pro_lcg2_config_site.tpl`. To start a new site, import the site paramater template [source:templates/trunk/sites/example/site/pro_lcg2_config_site.tpl example]. The list of all available variables with their description and their default value can be consulted in template source:templates/trunk/grid/glite-3.0.0/defaults/glite.tpl. '''This template is a critical part of standard templates and should not be modified or duplicated'''. 
 
 ''Note : Information in this page may document features or configuration options not present in the current release. These information are related to changes and improvement that will be available in next release and are already present in the [source:templates/branches/gLite-3.0.0 current development branch]. If you are urgently requiring these features, [wiki:Download/QWGTemplates use content] of this branch.''
@@ -181 +181 @@
 There is one template defining all the accepted CAs. We generally produced a new one each time there is a new release of the list of CAs officially accepted by EGEE. If you need to adjust it, create a site or cluster specific copy of `common/security/cas.tpl` in a directory `common/security`.
 
-If you need to update this template, refer to the standard [wiki:Development/AutoTemplates#TrustedCAsTemplate procedure] to do it.
+If you need to update this template, refer to the standard [wiki:Development/Templates/Generated#TrustedCAsTemplate procedure] to do it.