Re: [modwsgi] Re: Issue with mod_wsgi using trac and subversion 1.7
On Tue, Mar 27, 2012 at 10:20 AM, Graham Dumpleton
graham.dumple...@gmail.com wrote:
If you are able to modify and recompile mod_wsgi source code in your
setup, try modifying:
static const char * const p1[] = { mod_alias.c, NULL };
to:
static const char * const p1[] = { mod_alias.c, mod_dav_svn.c, NULL
};
This will ensure that SVN module gets a look in first.
I tried this but does not seem to work, one thing I have in my
configuration that my svn configurations are inside named vhost if that
makes a difference.
Graham
On 27 March 2012 15:22, vishwajeet singh dextrou...@gmail.com wrote:
On Tue, Mar 27, 2012 at 1:20 AM, Graham Dumpleton
graham.dumple...@gmail.com wrote:
I thought I already suggested playing with order of LoadModule lines
in Apache configuration, will need to check back in emails. I did
consider that likely order of one of the handlers, but based on
fiddling LoadModule lines not helping, seemed to be something else.
Is there a way to exclude some paths from wsgi handler ??
Problem is that instead of going to /svn/ it's getting matched to / which
the wsgi handler and this happens only for post requests which I fail to
understand, any suggestions to workaround this issue.
Graham
On 27 March 2012 05:27, Vishwajeet dextrou...@gmail.com wrote:
I am facing the same issue with django+apache+mod_wsgi+svn 1.7.
I posted it on svn mailing list and got following reply
mod_wsgi is probably intercepting the POST request intended for
mod_dav_svn and not passing it on. Subversion 1.7.0 had a similar
problem, it tried to process non-Subversion POST requests and produced
an error. The Subversion problem was fixed in 1.7.2. A code change
in
mod_wsgi is probably required. It may be possible to reorder the
modules in the apache config file.
On Mar 23, 2:14 am, Adrian Gschwend adrian.gschw...@comuno.org
wrote:
Hi group,
Just as a followup, I posted it on the apache list:
http://article.gmane.org/gmane.comp.apache.user/99368
cu
Adrian
--
You received this message because you are subscribed to the Google
Groups modwsgi group.
To post to this group, send email to modwsgi@googlegroups.com.
To unsubscribe from this group, send email to
modwsgi+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/modwsgi?hl=en.
--
You received this message because you are subscribed to the Google
Groups
modwsgi group.
To post to this group, send email to modwsgi@googlegroups.com.
To unsubscribe from this group, send email to
modwsgi+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/modwsgi?hl=en.
--
Vishwajeet Singh
+91-9657702154 | dextrou...@gmail.com | http://bootstraptoday.com
Twitter: http://twitter.com/vishwajeets | LinkedIn:
http://www.linkedin.com/in/singhvishwajeet
--
You received this message because you are subscribed to the Google Groups
modwsgi group.
To post to this group, send email to modwsgi@googlegroups.com.
To unsubscribe from this group, send email to
modwsgi+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/modwsgi?hl=en.
--
You received this message because you are subscribed to the Google Groups
modwsgi group.
To post to this group, send email to modwsgi@googlegroups.com.
To unsubscribe from this group, send email to
modwsgi+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/modwsgi?hl=en.
--
Vishwajeet Singh
+91-9657702154 | dextrou...@gmail.com | http://bootstraptoday.com
Twitter: http://twitter.com/vishwajeets | LinkedIn:
http://www.linkedin.com/in/singhvishwajeet
--
You received this message because you are subscribed to the Google Groups
modwsgi group.
To post to this group, send email to modwsgi@googlegroups.com.
To unsubscribe from this group, send email to
modwsgi+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/modwsgi?hl=en.
Re: [modwsgi] Re: Issue with mod_wsgi using trac and subversion 1.7
What are the names of all the DAV modules loaded in Apache?
It may not be mod_dav_svn that needs to be first but one of the core
DAV modules.
So in try mod_dav.c instead. Also maybe mod_dav_fs.
Graham
On 27 March 2012 17:01, vishwajeet singh dextrou...@gmail.com wrote:
On Tue, Mar 27, 2012 at 10:20 AM, Graham Dumpleton
graham.dumple...@gmail.com wrote:
If you are able to modify and recompile mod_wsgi source code in your
setup, try modifying:
static const char * const p1[] = { mod_alias.c, NULL };
to:
static const char * const p1[] = { mod_alias.c, mod_dav_svn.c, NULL
};
This will ensure that SVN module gets a look in first.
I tried this but does not seem to work, one thing I have in my configuration
that my svn configurations are inside named vhost if that makes a
difference.
Graham
On 27 March 2012 15:22, vishwajeet singh dextrou...@gmail.com wrote:
On Tue, Mar 27, 2012 at 1:20 AM, Graham Dumpleton
graham.dumple...@gmail.com wrote:
I thought I already suggested playing with order of LoadModule lines
in Apache configuration, will need to check back in emails. I did
consider that likely order of one of the handlers, but based on
fiddling LoadModule lines not helping, seemed to be something else.
Is there a way to exclude some paths from wsgi handler ??
Problem is that instead of going to /svn/ it's getting matched to /
which
the wsgi handler and this happens only for post requests which I fail to
understand, any suggestions to workaround this issue.
Graham
On 27 March 2012 05:27, Vishwajeet dextrou...@gmail.com wrote:
I am facing the same issue with django+apache+mod_wsgi+svn 1.7.
I posted it on svn mailing list and got following reply
mod_wsgi is probably intercepting the POST request intended for
mod_dav_svn and not passing it on. Subversion 1.7.0 had a similar
problem, it tried to process non-Subversion POST requests and
produced
an error. The Subversion problem was fixed in 1.7.2. A code change
in
mod_wsgi is probably required. It may be possible to reorder the
modules in the apache config file.
On Mar 23, 2:14 am, Adrian Gschwend adrian.gschw...@comuno.org
wrote:
Hi group,
Just as a followup, I posted it on the apache list:
http://article.gmane.org/gmane.comp.apache.user/99368
cu
Adrian
--
You received this message because you are subscribed to the Google
Groups modwsgi group.
To post to this group, send email to modwsgi@googlegroups.com.
To unsubscribe from this group, send email to
modwsgi+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/modwsgi?hl=en.
--
You received this message because you are subscribed to the Google
Groups
modwsgi group.
To post to this group, send email to modwsgi@googlegroups.com.
To unsubscribe from this group, send email to
modwsgi+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/modwsgi?hl=en.
--
Vishwajeet Singh
+91-9657702154 | dextrou...@gmail.com | http://bootstraptoday.com
Twitter: http://twitter.com/vishwajeets | LinkedIn:
http://www.linkedin.com/in/singhvishwajeet
--
You received this message because you are subscribed to the Google
Groups
modwsgi group.
To post to this group, send email to modwsgi@googlegroups.com.
To unsubscribe from this group, send email to
modwsgi+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/modwsgi?hl=en.
--
You received this message because you are subscribed to the Google Groups
modwsgi group.
To post to this group, send email to modwsgi@googlegroups.com.
To unsubscribe from this group, send email to
modwsgi+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/modwsgi?hl=en.
--
Vishwajeet Singh
+91-9657702154 | dextrou...@gmail.com | http://bootstraptoday.com
Twitter: http://twitter.com/vishwajeets | LinkedIn:
http://www.linkedin.com/in/singhvishwajeet
--
You received this message because you are subscribed to the Google Groups
modwsgi group.
To post to this group, send email to modwsgi@googlegroups.com.
To unsubscribe from this group, send email to
modwsgi+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/modwsgi?hl=en.
--
You received this message because you are subscribed to the Google Groups
modwsgi group.
To post to this group, send email to modwsgi@googlegroups.com.
To unsubscribe from this group, send email to
modwsgi+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/modwsgi?hl=en.
Re: [modwsgi] Re: mod_wsgi and apache vs. paster
Thanks very much. On 3/26/2012 3:28 PM, Graham Dumpleton wrote: See: http://code.google.com/p/modwsgi/wiki/TipsAndTricks#Determining_If_Running_Under_mod_wsgi Graham On 27 March 2012 03:02, Kentjkentbo...@gmail.com wrote: I found this: if shell in sys.argv: And I'll use that unless someone has a better way. Thanks! On Monday, March 26, 2012 11:46:07 AM UTC-4, Kent wrote: Graham, How can I detect from within my application whether it is being run by apache with mod_wsgi versus run by paster? I'm assuming there is a fairly nice way to determine this. Thanks for your time, Kent -- You received this message because you are subscribed to the Google Groups modwsgi group. To view this discussion on the web visit https://groups.google.com/d/msg/modwsgi/-/LLagqq3tvpUJ. To post to this group, send email to modwsgi@googlegroups.com. To unsubscribe from this group, send email to modwsgi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en. -- You received this message because you are subscribed to the Google Groups modwsgi group. To post to this group, send email to modwsgi@googlegroups.com. To unsubscribe from this group, send email to modwsgi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
[modwsgi] coverage
Has the situation with code coverage changed at all since the posts in 2010? -- You received this message because you are subscribed to the Google Groups modwsgi group. To post to this group, send email to modwsgi@googlegroups.com. To unsubscribe from this group, send email to modwsgi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
Re: [modwsgi] Re: coverage
Can you provide a link to posts in Google Group for mod_wsgi that you are referring to? Graham On 28 March 2012 10:44, bc craft.br...@gmail.com wrote: On Mar 27, 3:08 pm, bc craft.br...@gmail.com wrote: Has the situation with code coverage changed at all since the posts in 2010? I gave the following a try, which gave me some results (using daemon mode) Set WSGIDaemonProcess processes=1 threads=1, and restarted apache. Added django views to invoke coverage.start() coverage.stop()/save() Invoked the start view. integration tests Invoked the stop view. The results look promising. Is there anything I should watch out for with this approach? -- You received this message because you are subscribed to the Google Groups modwsgi group. To post to this group, send email to modwsgi@googlegroups.com. To unsubscribe from this group, send email to modwsgi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en. -- You received this message because you are subscribed to the Google Groups modwsgi group. To post to this group, send email to modwsgi@googlegroups.com. To unsubscribe from this group, send email to modwsgi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
[modwsgi] Re: coverage
http://groups.google.com/group/modwsgi/browse_thread/thread/58f41b009bf810cc/0c3f9871a4011857?lnk=gstq=code+coverage#0c3f9871a4011857 On Mar 27, 7:47 pm, Graham Dumpleton graham.dumple...@gmail.com wrote: Can you provide a link to posts in Google Group for mod_wsgi that you are referring to? Graham On 28 March 2012 10:44, bc craft.br...@gmail.com wrote: On Mar 27, 3:08 pm, bc craft.br...@gmail.com wrote: Has the situation with code coverage changed at all since the posts in 2010? I gave the following a try, which gave me some results (using daemon mode) Set WSGIDaemonProcess processes=1 threads=1, and restarted apache. Added django views to invoke coverage.start() coverage.stop()/save() Invoked the start view. integration tests Invoked the stop view. The results look promising. Is there anything I should watch out for with this approach? -- You received this message because you are subscribed to the Google Groups modwsgi group. To post to this group, send email to modwsgi@googlegroups.com. To unsubscribe from this group, send email to modwsgi+unsubscr...@googlegroups.com. For more options, visit this group athttp://groups.google.com/group/modwsgi?hl=en. -- You received this message because you are subscribed to the Google Groups modwsgi group. To post to this group, send email to modwsgi@googlegroups.com. To unsubscribe from this group, send email to modwsgi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
[modwsgi] Re: coverage
To be clear, I'm not using anything from that post. I'm just using the process I outlined, using the coverage start/stop/save methods from django view functions (while limiting apache to one thread). On Mar 27, 8:01 pm, bc craft.br...@gmail.com wrote: http://groups.google.com/group/modwsgi/browse_thread/thread/58f41b009... On Mar 27, 7:47 pm, Graham Dumpleton graham.dumple...@gmail.com wrote: Can you provide a link to posts in Google Group for mod_wsgi that you are referring to? Graham On 28 March 2012 10:44, bc craft.br...@gmail.com wrote: On Mar 27, 3:08 pm, bc craft.br...@gmail.com wrote: Has the situation with code coverage changed at all since the posts in 2010? I gave the following a try, which gave me some results (using daemon mode) Set WSGIDaemonProcess processes=1 threads=1, and restarted apache. Added django views to invoke coverage.start() coverage.stop()/save() Invoked the start view. integration tests Invoked the stop view. The results look promising. Is there anything I should watch out for with this approach? -- You received this message because you are subscribed to the Google Groups modwsgi group. To post to this group, send email to modwsgi@googlegroups.com. To unsubscribe from this group, send email to modwsgi+unsubscr...@googlegroups.com. For more options, visit this group athttp://groups.google.com/group/modwsgi?hl=en. -- You received this message because you are subscribed to the Google Groups modwsgi group. To post to this group, send email to modwsgi@googlegroups.com. To unsubscribe from this group, send email to modwsgi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
