An interesting set of questions, and one I've been thinking about myself. So here's my tuppence-worth.
Background: I've written a set of 3 websites, which I've developed incrementally, some shared code, some separate - done for my own benefit, no external customer, so I can change things as I see fit. It's a small project but one of the purposes is to work out how best to manage a larger project or set of websites which use a common base. > Revision Control: How do you layout your development repository? I'm > using Subversion for my setup but would be interested in hearing what > else others are using (Mercurial, Bazaar, Git, etc) svn for revision control. This is a very interesting article from James Bennett who's always worth listening to... http://www.b-list.org/weblog/2006/sep/10/django-tips-laying-out-application/ > Packaging: Django has an aversion to using setuptools and opts to > stick with the basics in distutils. What are you using for packaging > your application? What's the best way to deploy a Django project that My packaging is very simple - an upload script which does an svn update to get the current code, rips out the .svn stuff and any unwanted directories, then rsync up to the live host. No other packaging needed since I'm the only user :-) > Buildbot: Do you use Buildbot or something similar for your Django > development? How does that work for you? What other options are > there that would work well? I run my test prog regularly from a cron job. The test prog runs unit tests through the common code, and functional tests for the various websites. > Versioning: How do you mark versions of your Django project? Meaning, > how can you create your Django app so it has a version that you can > track within the application itself as well as for setting up > upgrades, etc? I can create something in __init__.py in the root of > my project but how does that work with the SCM? Since trunk is always > in development it would make sense to have something in there. Do you > keep it is a tag or branch? I'm new to this so hopefully I'm making > sense. I'd do a svn tag. > Migrations: What do you use to track database migrations? I know of > django-evolution, South and a few others but I really have no idea how > these function and which is the most mature. What do you have > experience with? Haven't found a good answer to this yet, although django-evolution looks interesting. I'm interested to hear how others do it all Rachel --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
