Before that someone starts working about this, you must consider this: 1. It's already has been created a project with that intention. Its name is capystrano [1] and althought has been not uploaded code -he could be working offline-, it would be best contact with its author to doesn't duplicate work.
2. If you think that capistrano -the original tool built with Ruby- is very complex, has been built a similar tool but more simple. It has been built too with Ruby in *only 4 days* and its name is Vlad the Deployer [2] [3]. 3. Has been created Webistrano [4], a Web UI for managing Capistrano deployments, and after to see the screencasts I would ask myself if the effort is worth the trouble to implement a tool thus when it would be possible to customize capistrano to deploy Django and then to use Webistrano. [1] http://code.google.com/p/capystrano/ [2] http://www.infoq.com/news/2007/08/vlad-the-deployer [3] http://rubyhitsquad.com/Vlad_the_Deployer.html [4] http://blog.innerewut.de/webistrano/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
