On Jul 10, 4:53 am, Chris <[EMAIL PROTECTED]> wrote:
> I'm trying to find the shortest path to hosting multiple projects with
> authentication that works and decent performance. I'm smart enough to
> insist on getting one project working before generalizing the set-up
> to handle multiple projects, but just barely. I've got a basic setup
> working for 3 projects using 3 virtual hosts, but...
>
> I'm having problems getting authentication working on Trac 0.10.4
> installed from RPM running under Apache using mod_python - No commits,
> no tickets, no Spam. It's slow too, but the mailing list archives seem
> to indicate that my issues using .htpasswd could be related to
> mod_python. Solution:mod_wsgi; That's cool - two birds, one stone...
> right? There's a hitch. Installation from RPM means no Eggs, right? So
> what that mean for the wsgi script? Pointing ['PYTHON_EGG_CACHE'] in
> the os.environ to the site packages directory only succeeded in
> rapidly expanding the Apache error log.
The Python egg cache has to be a directory that user code under Apache
can write to. It also should not be pointed at site-packages directory
but somewhere else which is specific to that user.
Graham
> 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?
>
> What do I need to do to get cooking?
>
> Chris
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac
Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---
