Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Trac: Users

two different tracs, but one apache only

 

 

Trac users RSS feed   Index | Next | Previous | View Threaded


R.Sokoll at intershop

Nov 14, 2007, 6:29 AM

Post #1 of 3 (200 views)
Permalink
two different tracs, but one apache only

Hi,

is $SUBJECT possible?
Background: I need to check whether all my plugins will work with the
current .11 trunk.
Right now, I'm on 0.11dev-r6137, but AFAIK, with r6138, the API has
been changed, and some plugins may stop working correctly.
If I use for example

<Location /tractest>
[...]
PythonPath "sys.path + ['/path/to/my/brandnew/trac']"
[...]
</Location>

my old trac is still in sys.path, correct? If so, which one will be
used?
Is there any other way beside using a second instance of apache and a
second python installation?

Rainer

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To post to this group, send email to trac-users [at] googlegroups
To unsubscribe from this group, send email to trac-users-unsubscribe [at] googlegroups
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---


Graham.Dumpleton at gmail

Nov 14, 2007, 1:49 PM

Post #2 of 3 (197 views)
Permalink
Re: two different tracs, but one apache only [In reply to]

On Nov 15, 1:29 am, Rainer Sokoll <R.Sok...@intershop.de> wrote:
> Hi,
>
> is $SUBJECT possible?
> Background: I need to check whether all my plugins will work with the
> current .11 trunk.
> Right now, I'm on 0.11dev-r6137, but AFAIK, with r6138, the API has
> been changed, and some plugins may stop working correctly.
> If I use for example
>
> <Location /tractest>
> [...]
> PythonPath "sys.path + ['/path/to/my/brandnew/trac']"
> [...]
> </Location>
>
> my old trac is still in sys.path, correct? If so, which one will be
> used?
> Is there any other way beside using a second instance of apache and a
> second python installation?

You can't do it with mod_python.

The primary reason is that if using Trac in conjunction with
Subversion, then to be safe and avoid potential problems with Python
bindings for Subversion, you must force mod_python to run Trac in the
main interpreter. In doing this though it will not be possible to be
using two different versions of Trac for different instances.

If only wishing to test stuff, you could always just run Trac through
CGI. It will be slow but allow you to easily run it with different
versions of the software you want to test.

Another alternative for Apache is to use mod_wsgi (http://
www.modwsgi.org) instead. Using its daemon process mode it is possible
to farm off distinct Trac instances to different daemon processes.
Because they are in different processes you can safely run them in the
main interpreter but also have them use different versions of software
through appropriate setup of sys.path. To be absolutely safe and avoid
problems if Trac is still installed in global site-packages, then
mod_wsgi can be used in conjunction with Python virtual environments
such as virtualenv.py (http://pypi.python.org/pypi/virtualenv).

So perhaps just use CGI, but if interested in how to do it in
mod_wsgi, can point out relevant documentation and step you through
it.

Graham


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To post to this group, send email to trac-users [at] googlegroups
To unsubscribe from this group, send email to trac-users-unsubscribe [at] googlegroups
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---


rupert.thurner at gmail

Nov 15, 2007, 11:25 AM

Post #3 of 3 (191 views)
Permalink
Re: two different tracs, but one apache only [In reply to]

the easiest might be to
* easy_install --install_dir the plugins
* set python_path
* run "nohup tracd", i.e. trac standalone
* maybe put apache cgi / proxy if you really want to have it
reachable via apache

unfortunately there was no tag when changing the api ... and no
possibility to mark the plugins as working or not working.

rupert.

On Nov 14, 3:29 pm, Rainer Sokoll <R.Sok...@intershop.de> wrote:
> Hi,
>
> is $SUBJECT possible?
> Background: I need to check whether all my plugins will work with the
> current .11 trunk.
> Right now, I'm on 0.11dev-r6137, but AFAIK, with r6138, the API has
> been changed, and some plugins may stop working correctly.
> If I use for example
>
> <Location /tractest>
> [...]
> PythonPath "sys.path + ['/path/to/my/brandnew/trac']"
> [...]
> </Location>
>
> my old trac is still in sys.path, correct? If so, which one will be
> used?
> Is there any other way beside using a second instance of apache and a
> second python installation?
>
> Rainer
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To post to this group, send email to trac-users [at] googlegroups
To unsubscribe from this group, send email to trac-users-unsubscribe [at] googlegroups
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Trac users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.