i've make a bunch of changes but it didn't seem to do anything for
me.  the new ticket page just took 17 secs to be severed.

my httpd.conf is now;

 <VirtualHost  172.16.94.25:80 >

    DocumentRoot /var/trac
    ServerName trac.autoreturn.com
    ServerAlias trac
    ServerAdmin [email protected]

    # Configure basic resources for TRAC
    Alias /trac /usr/share/trac/htdocs
    Alias /css /usr/share/trac/htdocs/css
    Alias /chrome/ /var/www/agilo_static/htdocs/

WSGIScriptAlias / /var/trac/agilo_static/cgi-bin/trac.wsgi

<Directory /var/trac/agilo_static/cgi-bin >
    WSGIApplicationGroup %{GLOBAL}
    Order deny,allow
    Allow from all
</Directory>

    <LocationMatch "/[[:alnum:]]+/login" >
        AuthType Basic
        AuthName "The Trac Server"
        AuthBasicProvider ldap
        AuthzLDAPAuthoritative on
        Require ldap-group
cn=grp_it_dev,ou=groups,ou=AutoReturn,dc=autoreturn,dc=com
    </LocationMatch>

</VirtualHost>

i even ran a vacuum and re-index on the database.  when i hit the
burndown chart i see httpd goto 100% CPU in top.

this machine is a VM but has a bunch of CPU and 2gigs of ram allocated
to it.  what else could be wrong?

thanks,
deno




On Oct 14, 4:16 pm, deno <[email protected]> wrote:
> how do i configure httpd to use mod_wsgi for trac/agilo ?
>
> i got the mod installed but not sure on the config.
>
> thanks,
>
> On Oct 14, 3:09 pm, Andrea Tomasini <[email protected]>
> wrote:
>
> > On 14 Oct, 2009, at 23:19 , deno wrote:
>
> > Hi deno,
>
> > > so i decided to upgrade in hope that i could get agilo to run faster.
> > > right it it takes several seconds (5-10) for almost any operation.  i
> > > also get the trac logo icon in the upper left of the screen and no the
> > > agilo logo.
>
> > Well 5-10 seconds is really a lot of time... what we do in production  
> > systems (like our hosted Agilo - that uses mod_wsgi) is to deploy all  
> > the static content in a separate folder and let Apache serve it.  
> > Normally this accelerate the performances, but I do not think in your  
> > case will solve it.
>
> > Anyway the tip is good for everyone, so you can try:
> > 1) Download the source of Agilo (latest)
> > 2) look in the script folder and you will find a trac_deploy.py script
> > 3) use the command as:
>
> > $ python trac-deploy.py <env> deploy <static_folder>
>
> > This should deploy all the static files of your trac/agilo  
> > installation to the "static_folder"
>
> > 4) map apache to point there:
>
> > Alias /chrome/ /var/www/agilo_static/htdocs/
>
> > <Location /chrome/>
> >         SetHandler None
> > </Location>
>
> > I don't know why you put also the path /trac/ with no handler... but  
> > may be you know that ;-)
>
> > 5) restart apache ;-)
>
> > This should guarantee you that trac will not serve static files  
> > anymore...
>
> > This script will be available as a patch to trac-admin.py starting  
> > from trac 0.11.6, this is why we didn't publish this yet ;-)
>
> > HTH
> > Best
> > ANdreaT
--~--~---------~--~----~------------~-------~--~----~
Follow Agilo on Twitter: http://twitter.com/agiloforscrum
-----
You received this message because you are subscribed to the Google
Groups "Agilo for Scrum" group. This group is moderated by agile42 GmbH 
http://www.agile42.com and is focused in supporting Agilo for Scrum users.
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/agilo?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to