83 | | == Example == |
| 84 | !TracLegos is designed so that site-specific configuration does not need to (and really shouldn't) live in the templates but can live in its own {{{.ini}}} file. The advantages of this is that templates from XYZcorp can be shared with ABCcorp without modification but that a policy for trac project creation can be effectively enforced as well as having the convenience of domain-specific variables by using a site configuration {{{.ini}}} file (or files). |
| 85 | |
| 86 | Variables are currently supported in a site configuration file. See source:traclegosscript/anyrelease/example/site_example.ini for the format of this file. Using the command line, site configuration {{{.ini}}} files are specified with the `-c` option: |
| 87 | |
| 88 | {{{ |
| 89 | create-trac-project -c example/site_example.ini ... |
| 90 | }}} |
| 91 | |
| 92 | Configuration files may also be specified for the web front-end ''(not yet implemented! see #3761)''. To use this, add the following option to the {{{.ini}}} file specified for `paster serve`: |
| 93 | |
| 94 | {{{ |
| 95 | traclegos.conf = /path/to/site_example.ini, /path/to/myorganization.ini |
| 96 | }}} |
| 97 | |
| 98 | |
| 99 | == Examples == |