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: certain configurations and changes to settings, creating an apps directory (module), 404 and 500 templates, etc. So what I do now is I have a separate project, which I call django-skel, that is just a new project file layout with the changes I already want to make for every project. For each new project, I just export from that, copy the files into the new project space, and commit. 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? Or do you have some different approach that solves this problem for you? Thanks, Aaron -- Aaron Maxwell http://redsymbol.net/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
