-1. The only issue that I have with sites is that the default site should be 127.0.0.1:8000 since that's what runserver defaults to. Putting example.com as SITE_ID 1 only makes novice django developers shout and throw things because like me they 'add 127.0.0.1:8000 and delete example.com' instead of replacing example.com and wonder why runserver isn't serving their first hello world flatpage. I had a blog post which included this tip, and it amazes me how many people commented they had done the same thing, which suggests there is a large number of people who make this simple but avoidable mistake. Since nobody will ever use 'example.com' it should not be there in the first place.
On May 24, 12:16 pm, Rolando Espinoza La Fuente <dark...@gmail.com> wrote: > On Tue, May 18, 2010 at 11:14 AM, Felipe Prenholato > > <philipe...@gmail.com> wrote: > > About idea of use settings.py to set a default site, -1 > > About ask to user what is yours default site, +1 > > This thing only runs at syncdb, so I really don't think that a entry in > > settings.py is needed. > > This seems a controversial topic :) > > +1 to the idea to just ask in syncdb, in the same way that admin user > is created. > Here is my proposal:http://gist.github.com/411456 > > Regards, > > ~Rolando > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To post to this group, send email to django-develop...@googlegroups.com. > To unsubscribe from this group, send email to > django-developers+unsubscr...@googlegroups.com. > For more options, visit this group > athttp://groups.google.com/group/django-developers?hl=en. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
