On Thu, Sep 13, 2012 at 4:25 AM, DJ-Tom <eventel...@gmail.com> wrote: > Basically I always try to have the same environment for development as I > also use for actual production - I'm lucky that my projects are small enough > so i can do that :-) to avoid last minute surprises when trying to deploy > the application to the public.
This is a fine thing to do once you understand Django and know what you're doing with it. But for a beginner's tutorial aimed at someone who knows nothing about Django, the development server is far more ideal since it avoids throwing in a pile of "oh, and before you even start, go learn how to set up and run Apache and a bunch of other stuff so that you can use a production server stack to learn Django" :) As such, the tutorial doesn't and shouldn't mention trying to set up Apache or other production deployment setups. It should simply teach people how to write Django applications and understand how the pieces of the framework fit together. -- 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.
