On Tue, Jan 13, 2009 at 7:45 PM, mguthrie <mitchguth...@gmail.com> wrote:
> > 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) I have django and third party apps checked out via svn into my development folder. so I can update those when I want to. then I git that whole stack I push that to a (bare) git repos on one of my servers (bare means that it isn't a working copy, its just the files, like an svn server) and use fab / fabric to do the deployment. that means on my local machine: fab pushpull does a git push (from local checked in changes up to the repository) does a git pull (from the respository on the remote server into my actual deployment folder incidentally on the same server) and then restarts apache does the deployment. fab is in alpha and is changing, but I like its direct simplicity. later I will probably do different branches on the git stack that include / exclude different sites / apps so that whatever I'm deploying is just the code that that site (or cluster of sites) needs I'm still not completely at peace with this solution but it has worked quite well so far. -fx > > > 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 > would make it easy on the end user to install and configure? I don't > really care about providing individual apps. I wish to deploy my > application in it's entirety. It would be nice if this could be > worked into the development process. Pylons and Turbogears seem to > have a nice process setup using Paste and virtualenv that works well > for the development and testing process. Do Django users have > something similar? > > 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? > > 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. > > 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? > > That's probably plenty for this post. Sorry it's so long but this is > difficult stuff and it's spread out across the internet. Not to > mention that it's not specific to Django development. > > I've recently worked with a Java developer and got a chance to see his > development process and was really impressed. Java seems to have more > tools available that tie in nicely with each other for continuous > integration. He was using Trac, Buildbot, Unit testing (JUnit) and > had scripts to deploy to a new server immediately. It was pretty > impressive and I would like to know if anyone has something similar > setup for their Django projects. > > Thanks in advance for any input. > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
