Ask HN: Django continuous deployment

Hello all! I am currently working part-time on my first startup and I've hit my first snag that can't be solved by "coding more".

The question concerns continuous deployment, I love the company structure of Etsy and feel that their kind of development suites my personality very well. So I would like to try my hand at continuous deployment.

I am using django as my web framework and have had a lot of success in the past for building quick sites for friends and family.

I currently have a two tree development, a "frontpage" and a "master". The frontpage is not moving and only contains enough backend to run my landing page/beta testing scripts. But I am getting closer to MVP and I would like to replace the frontpage with a moving "master". This master would maintain the frontpage/beta testing scripts but allow logins for initial first adopters.

I have looked into migration addons such as: django-south and django-evolution. And I am currently at a good crossroads to implement one of them.

I am asking the community for their general experiences implementing continuous deployment and any django specific continuous deployment schemes.

Thanks!