trac-users

Chris Babcock wrote:
> On Wed, 09 Jul 2008 23:16:23 -0700
> Noah Kantrowitz <[EMAIL PROTECTED]> wrote:
>
> > > Pointing ['PYTHON_EGG_CACHE'] in
> > > the os.environ to the site packages directory only succeeded in
> > > rapidly expanding the Apache error log.  
> > 0.10 does not install as an egg ever. setuptools integration is new
> > in 0.11. You should be setting PYTHON_EGG_CACHE to /tmp unless you
> > have a very good reason not to (or the equivalent on windows).
>
> That did the trick, thank you very much. It's still a little sluggish,
> but not much slower than PHP. Logging in works, so I can create users to
> edit tickets. That's the main thing. Software you can use *and* keep
> your hair. Nice.
>
> > > When I've implemented Python servers before, I've always just used
> > > mod_proxy. Is it possible to write to the SVN repository running
> > > Trac as a stand alone program? If I do that, will I have to run a
> > > separate instance of tracd for each project?  
> > You can certainly use tracd for multiple projects. I don't understand 
> > your question about Subversion though, Trac never writes to
> > subversion for any reason.
>
> That was my misunderstanding about the scope of the project. If there
> are no plug-ins to manipulate repositories already in the works then
> I'll have to look for other ways to get the soup-to-nuts functionality
> I want. I think that there are packages that can do commits in
> SVN... and that one of them uses Trac on its development site. :-)
>
> I'd certainly appreciate a pointer to whatever plug-in or external
> programs do this well with Trac (or failing that, do it poorly but
> demonstrate potential for improvement).

I've never heard of anything that replaces mod_dav_svn, which it sounds 
like you want. Trac is designed to work alongside a Subversion RA 
server, not replace it.

--Noah