Re: [Proposal] Adding optional SITE_DOMAIN and SITE_NAME variables in settings.py

2010-03-15 Thread Yuri Baburov
Hello all, How do you like the following idea: startproject command puts a fixture for django.contrib.sites (and fixture for superuser probably) to the root folder or whatever, to be loaded with syncdb? That way also encourage users to get more familiar with fixtures. Of course it's too far for 1.

Re: [Proposal] Adding optional SITE_DOMAIN and SITE_NAME variables in settings.py

2010-03-15 Thread David Larlet
Le 14 mars 2010 à 12:27, James Bennett a écrit : > On Fri, Mar 12, 2010 at 4:39 PM, aditya wrote: > >> Currently, Django uses "example.com" for both the domain and the >> name. The only way to change that is to wade into the actual >> database. > 2. If it turns out there's a real problem, prov

Re: [Proposal] Adding optional SITE_DOMAIN and SITE_NAME variables in settings.py

2010-03-14 Thread James Bennett
On Fri, Mar 12, 2010 at 4:39 PM, aditya wrote: > The trouble is, there is no straightforward way to configure the name > and domain of a site. Sure there is: create a Site object, or edit an existing one, setting the values you want on it. > Currently, Django uses "example.com" for both the doma

Re: [Proposal] Adding optional SITE_DOMAIN and SITE_NAME variables in settings.py

2010-03-12 Thread Rajeev J Sebastian
On Sat, Mar 13, 2010 at 3:09 AM, aditya wrote: > Description > = > This page of the Django documentation shows how to use the 'Sites' > framework to get the domain of the current site: > > http://docs.djangoproject.com/en/dev/ref/contrib/sites/ > > I've noticed that 'domain = Site.objects.

[Proposal] Adding optional SITE_DOMAIN and SITE_NAME variables in settings.py

2010-03-12 Thread aditya
Description = This page of the Django documentation shows how to use the 'Sites' framework to get the domain of the current site: http://docs.djangoproject.com/en/dev/ref/contrib/sites/ I've noticed that 'domain = Site.objects.get_current().domain' is becoming a common idiom in Django. Mo