Related reading: http://blog.dscpl.com.au/2010/03/improved-wsgi-script-for-use-with.html http://blog.dscpl.com.au/2008/12/using-modwsgi-when-developing-django.html http://blog.dscpl.com.au/2009/02/source-code-reloading-with-modwsgi-on.html
Graham On Saturday, August 7, 2010, [email protected] <[email protected]> wrote: > > On Aug 6, 2010, at 11:06 AM, Carl Nobile wrote: > >> The built in web server in Django has issues. If you write your code >> to work only with the built in server it may not work correctly when >> you need to go to production. Djangos web server does a lot of setup >> for you completely hidden from your eyes, and may not work without >> some fiddling when you go to mod_wsgi/apache. My rule of thumb is if >> you are writing code that will eventually see the light of day in a >> production environment then setup the WSGI stuff first and develop in >> a real mod_wsgi/apache environment so there will not be any surprises >> when you go live. > > I'm with you on that one... > > Last thing you need is a multitude of potentially unrelated, cascading issues > when you go to actually deploy while having no experience actually solving > them, or even knowing where to begin. > > Better to handle those issues as you develop so you can see which change > leads to what problem and solve them as you go. > > S > > -- > You received this message because you are subscribed to the Google Groups > "modwsgi" group. > 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/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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
