On 17/06/2012 7:30am, Laurence MacNeill wrote:
> Ok... I'm still learning this stuff here, and I'm confused about one
> thing... Well, many things, actually, but only one thing that I'll
> ask about here.
>
> During the tutorial I have to type "python manage.py runserver" in
> order to see my django pages in a web-browser. Obviously, I don't
> want to do this for anything but the tutorial... In fact, I don't
> even want to do this for the tutorial -- I have apache and mod_wsgi
> already running on this machine, so why won't those things just
> automatically serve up these django pages I'm creating? What more do
> I need to do to get apache and mod_wsgi to server my django pages?
https://docs.djangoproject.com/en/dev/howto/deployment/wsgi/
Go right ahead. It is a good thing to do. But you still need manage.py
runserver for development because it is specially designed to prioritise
debugging over security and performance. By default it uses port 8000 so
you can have Apache serve on port 80 or something else and have both
servers running the same code for comparison of output at the same time.
You enjoy the difference when Apache says "500" and manage.py runserver
says where your code is awry.
>
> Thanks,
> Laurence MacNeill
> Mableton, Georgia, USA
>
> --
> You received this message because you are subscribed to the Google
> Groups "Django users" group.
> To view this discussion on the web visit
>
https://groups.google.com/d/msg/django-users/-/XyTCXN8L3FIJ.
> To post to this group, send email to
django...@googlegroups.com.
> To unsubscribe from this group, send email to
>
django-users...@googlegroups.com.
> For more options, visit this group at
>
http://groups.google.com/group/django-users?hl=en.