3 ms·

I work with Django for a living but the lack of init/buildout in a new project has always driven me a bit nuts, I guess it's one of my development pet-peeves.

by tvon 17y ago

I work with Django for a living but the lack of init/buildout in a new project has always driven me a bit nuts, I guess it's one of my development pet-peeves. I've never had project that didn't need: - a project-wide templates/ directory - media/[css|img|js] directories - some kind of database setup by default - contrib.admin (well, I created a form mailer once that had no admin) Django seems to take a "we don't want to force you to use any particular setup" stance, but the result seems to be to force you to make a bunch of relatively meaningless decisions before you can start writing code. (they could have other reasons, I haven't looked into it lately) These days I have a script that does all this, and I know others have written similar scripts as well. It just strikes me as being a gaping hole on the Django development model... IMO anyway.

ubernostrum 17y ago
And your script probably sets things up differently from everyone else's :) But if you think it's a problem, why not publish whatever you use and encourage others to use it as well? (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)
- tvon 17y ago
  > 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.

by tvon 17y ago

ubernostrum 17y ago

And your script probably sets things up differently from everyone else's :) But if you think it's a problem, why not publish whatever you use and encourage others to use it as well? (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)

tvon 17y ago
> 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.