Graham Dumpleton wrote:
2009/3/31 Michael Schurter michael.schur...@gmail.com:
On Mon, Mar 30, 2009 at 1:50 PM, Robert Coup
robert.c...@koordinates.com wrote:
Hiya,
On Tue, Mar 31, 2009 at 12:09 AM, Graham Dumpleton
graham.dumple...@gmail.com wrote:
In the interests of promoting
I have created tar ball of first release candidate for 2.4. It is called:
mod_wsgi-2.4c1.tar.gz
and can be obtained from:
http://code.google.com/p/modwsgi/downloads/list
Have done a release candidate even though only a patch update as there
have been a lot of patches applied and want this
Hello Graham-- Late last night before falling asleep I realized that this
could be the only explanation, and suddenly realized that-- in fact-- the
very .wsgi file I wanted to test was called django.wsgi, which I had
renamed to django.py for something of a unit-test. Therefore, my import
was
r...@r12276:~/mod_wsgi-2.4c1# CFLAGS=-O2 ./configure --with-python=/
usr/bin/python3.1 --with-apxs=/usr/httpd/bin/apxs
checking Apache version... 2.2.11
configure: creating ./config.status
config.status: creating Makefile
r...@r12276:~/mod_wsgi-2.4c1# make
/usr/httpd/bin/apxs -c
2009/4/1 gert gert.cuyk...@gmail.com:
r...@r12276:~/mod_wsgi-2.4c1# CFLAGS=-O2 ./configure --with-python=/
usr/bin/python3.1 --with-apxs=/usr/httpd/bin/apxs
checking Apache version... 2.2.11
configure: creating ./config.status
config.status: creating Makefile
r...@r12276:~/mod_wsgi-2.4c1#
Django finally suggesting use of mod_wsgi over mod_python. :-)
http://docs.djangoproject.com/en/dev/howto/deployment/
Graham
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
modwsgi group.
To post to this group,
On Tue, Mar 31, 2009 at 2:07 PM, Graham Dumpleton
graham.dumple...@gmail.com wrote:
Django finally suggesting use of mod_wsgi over mod_python. :-)
http://docs.djangoproject.com/en/dev/howto/deployment/
Finally! Good work Graham! You made a project so good they could no
longer ignore it!
Yes, I did. Now that you mention it, I am not sure why I felt I needed to
do that.
... Something must have prompted me to do it, but I cannot remember now. It
must have had something to do with seeing the following example line:
os.environ['DJANGO_SETTINGS_MODULE'] =
2009/4/1 Tim Valenta tonightslasts...@gmail.com:
Yes, I did. Now that you mention it, I am not sure why I felt I needed to
do that.
... Something must have prompted me to do it, but I cannot remember now. It
must have had something to do with seeing the following example line:
Hmmm, that crappy setup information is in:
http://code.djangoproject.com/wiki/django_apache_and_mod_wsgi
I'll fix it up.
:-(
Graham
2009/4/1 Graham Dumpleton graham.dumple...@gmail.com:
2009/4/1 Tim Valenta tonightslasts...@gmail.com:
Yes, I did. Now that you mention it, I am not sure
On Mar 31, 10:27 pm, Graham Dumpleton graham.dumple...@gmail.com
wrote:
2009/4/1 gert gert.cuyk...@gmail.com:
r...@r12276:~/mod_wsgi-2.4c1# CFLAGS=-O2 ./configure --with-python=/
usr/bin/python3.1 --with-apxs=/usr/httpd/bin/apxs
checking Apache version... 2.2.11
configure: creating
2009/4/1 Tim Valenta tonightslasts...@gmail.com:
Unless I've made a mistake in my thinking, I believe that the
IntegrationWithDjango page also states that you should put that ./apache/
directory in your apache conf
(http://code.google.com/p/modwsgi/wiki/IntegrationWithDjango)
2009/4/1 Tim Valenta tonightslasts...@gmail.com:
So then to clear up a little confusion from my end.. is there any need to be
putting that ./apache/ directory in the apache conf at all,
Yes, there must be a Directory container as previously showed for the
'apache' directory. This is required
2009/3/31 John Francis Lee j...@robinlea.com:
I have come to the conclusion that I should stop being good and trying
to save people from their code screwing up on CGI/WSGI adapters. The
real thing that should be fixed is the CGI/WSGI adapters. This isn't
really my problem to do anything
2009/4/1 Graham Dumpleton graham.dumple...@gmail.com:
2009/3/31 John Francis Lee j...@robinlea.com:
I have come to the conclusion that I should stop being good and trying
to save people from their code screwing up on CGI/WSGI adapters. The
real thing that should be fixed is the CGI/WSGI
2009/4/1 Tim Valenta tonightslasts...@gmail.com:
One final hurrah for the import error. So I've gotten everything running
this evening (thanks to direction given previously). The last thing I'm
noting is this:
My setup isn't particularly strange, in my opinion, yet I needed to add one
more
2009/4/1 Tim Valenta tonightslasts...@gmail.com:
Hm... yes, I had read that before, but I hadn't immediately caught the
reference to the fact that /usr/local/django was itself the document root.
I (personally) would suggest making a slight alteration to that
documentation, simply to state
17 matches
Mail list logo
