> 3) Modifying the production database as necessary. There's one major problem point in making this happen: Rails' migrations. It's pretty simple really, once laid out.
Beside svn & tar methods, this is one of the most complex point of this project, and it's also one of the points I'd need most help. > Would it not be > better to look at writing a django recipe for capistrano rather than > trying to re-implement it? Also, we can use a ferrari to drive heavy cargo. It's not really about "can I use it", but more about "will it be really useful? easy to use? what degree of easing will i achieve?"... you get it. Also, I think the community will benefit from such a tool. Deploying a django project has always been a complex point in my early days with it. Making tasks to automate server setups would also be a great plus point for all the django newbies. I think merging all of these ideas into one big django-addon would be a gorgeous idea for all of us. Not only rails is fun! --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
