On Mon, Mar 26, 2012 at 5:14 AM, Reinout van Rees <rein...@vanrees.org> wrote: > In 1.3, there was no wsgi file. So either you added it yourself or > webfaction automatically adds it. > 1.4 started adding that wsgi.py file. It should be a drop-in replacement for > the one you have now, basically. > (Only thing to watch out for: wsgi.py hardcodes settings.py, so if you want > to use a productionsettings.py or so you should take a good hard look).
Thank you Reinout! I really appreciate the explanation. :) I will use the wsgi.py as a replacement and see how it goes. Much appreciated. Have a great day! Cheers, Micky -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.