Ilias Lazaridis wrote:
>> Switching between several trac versions should be simplified, even if
>> those are pulled from the SVN.
>>
> ...
> I just realized that this behaviour is already implemented:
>
> http://trac.edgewall.org/browser/trunk/trac/config.py?rev=3744#L427
>
> thus my problem is already solved.
>
Well spotted, I was not even aware of that!
My problem was that I often started with a `python setup.py install`,
right after a checkout. This creates a trac/siteconfig.py (and
trac/siteconfig.pyc), and after that, switching from one checkout to
another was not as simple as it could have been. After removing those
files, I can indeed run Trac straight from the repo, a quite useful
feature indeed.
There are some additional subtleties with the templates directory:
- the [trac] templates_dir configuration option can mask the default
location for templates, as:
templates_dir = Option('trac', 'templates_dir',
default_dir('templates'), ...
Since this option is usually set to the default value given at
'initenv' time, you'll have to comment it out from the trac.ini
for the default_dir('templates') to take effect.
- the local $TRAC_ENV/templates takes precedence over the above one.
There's a ticket stating the opposite [1], but it worksforme, though.
One problem I've noticed is that if you put one template there (say
error.html), then the included templates also needs to be located
there (in this case, layout.html), otherwise you'll get an error.
Conversely, if you only put the included template there (e.g. a
modified layout.html), it won't take precedence over the one located
in the same folder as the requested one (say the installed
wiki_view.html which hasn't been copied in $TRAC_ENV/templates).
And for those who haven't noticed yet, there's also the very useful
`[trac] auto_reload` configuration option that you can change to 'true'.
This makes the development of templates more comfortable: as you can
guess from the option name, this activates the auto-reload feature of
the Genshi TemplateLoader, which means templates are parsed again if a
modification was detected.
This, combined with the '-r' (auto-reload) option of tracd, makes Trac
development a very reactive process.
-- Christian
[1] http://trac.edgewall.org/ticket/3865
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac
Development" group.
To post to this group, send email to trac-dev@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/trac-dev
-~----------~----~----~----~------~----~------~--~---
