On Tuesday, September 4, 2012 11:43:53 AM UTC+5:30, Daniel Roseman wrote: > > On Tuesday, 4 September 2012 03:32:08 UTC+1, ecs1749 wrote: >> >> Thanks for the reply. Yes, I saw that message. I am a bit lost where to >> go next if I completely ignore that tutorial regarding doing admin from the >> development server (which I don't have). Do I dive into tutorial #3 and >> hope that it will pick up the admin stuff later when it gets to talk about >> wsgi? Or is there a "here's what you do if you don't have a development >> server" tutorial somewhere? >> >> > You should not be doing the tutorial - or any development - on your > server. Install Django locally and do it there, then deploy when you are > ready and not before. >
I have used the development server to run a test site so the client could see the site easily. It sat behind a real webserver: if you do this you can tighten security a bit (e.g. use http authentication to limit access). > > However, you are wrong to assume that the admin console has anything to do > with the development server - it works just fine with any server. > -- > DR. > -- 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/-/6P-djImkSIAJ. 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.
