Do you use a skeleton for new django sites?

Hi all, When creating a new django based website, my first step used to be to invoke "python manage.py startproject". The files created would be the first or second commit into version control for that project. I found, however, that I would always make a similar set of changes right after:

Re: Do you use a skeleton for new django sites?

On Tuesday 02 June 2009 22:09:03 Aaron Maxwell wrote: > Over time, I'll discover something new I'll want to add to all my django > sites.  So I just make that change to django-skel and forget about it. > > Does anyone else follow this technique? yes - I have only used the startproject startapp th

Re: Do you use a skeleton for new django sites?

I used to use a skeleton, but the problem was that I couldn't easily upgrade the already "forked" projects to a newer version of the skeleton; I had to manually backport all changed to each project. The solution I finally adopted is to have a wrapper for site configuration (settings and urls) as