On 1/6/06, Joseph Kocherhans <[EMAIL PROTECTED]> wrote: > Should sites be installed by init? I think it's used rarely enough > that it shouldn't.
It's used by various bits and pieces, such as the RSS and redirect frameworks, that need to know the fully-qualified domain name for an object. Maybe those frameworks could be slightly refactored to check that the sites app is installed (see http://code.djangoproject.com/ticket/1179 ). If the sites app isn't installed, they could simply use the current domain according to request.META['SERVER_NAME']. > Also, I think init should install admin as well, > but maybe there should be something like an init-noadmin command as > well in that case. That gets a bit too specific and special-case-ish. Two choices -- "init" and "init-light" (or whatever it's called) -- is as many as we should have. > It'd be nice to remove a couple of steps from the > tutorials (django-admin.py install admin, add django.contrib.admin to > INSTALLED_APPS), but it's at the expense of people who don't want the > admin, but *do* want sessions, auth, etc. The planned way to do this is to make "django-admin.py install" add the appropriate line to INSTALLED_APPS by editing the file and adding an "INSTALLED_APPS +=", like so: INSTALLED_APPS += 'django.contrib.admin' That removes the need to edit the settings file to add stuff to INSTALLED_APPS. Adrian -- Adrian Holovaty holovaty.com | djangoproject.com | chicagocrime.org
