> And your script probably sets things up differently from everyone else's :) I don't doubt it. Much like how there is the occasional "this is how I handle ma

> And your script probably sets things up differently from everyone else's :) I don't doubt it. Much like how there is the occasional "this is how I handle managing multiple settings for different systems" blog post, people have come up with their own systems because Django provides none. > But if you think it's a problem, why not publish whatever you use and encourage others to use it as well? http://github.com/tvon/django-gig http://github.com/tvon/django-gig Written for personal use, so... There is also "create project" or "project template", I forget the exact name, but it's on bitbucket or github... and "paster" from zopeskel seems to have potential to do something like this but it may be too zope specific, I don't know. There are ways to do it, but IMO it's something the framework should be handling. As it stands, "basic setup and configuration" is a much higher hurdle in Django than it is in Rails. > (also, FWIW I don't have such a script -- a new site at work always simply inherits default settings from other stuff, and those defaults are set up to match how our production servers work) Well, you don't have a script that builds things out in a certain way, but you have a system in place that handles project defaults.