Re: Deploying Feature in manage.py
On Oct 24, 2:18 pm, Markus Gattol wrote: > I agree with others that this is better left to tools such as fabric/cuisine > as they are build to handle these kind of > tasks:http://readthedocs.org/docs/fabric/en/latest/api/contrib/project.html There's indeed no generic way of deploying for everyone... I'm currently finishing a new deployment framework at my company (Mobile Vikings), inspired by fabric and also based upon Paramiko (the SSH) library. (It is not to reinvent Fabric, but we just needed our deployments to be more flexibility/powerful. That is as declarative as possible, readable, DRY and having reusable components, taking care of cross-server dependencies/references, undo where possible, having a deployment shell with autocomplete, easy beta/staging duplication, and more...) If everything goes well and I'm confident, we will place the stable source code on github and I'll post a link in django-users -- hopefully somewhere within the following two weeks. By the way, any input of what you think a deployment tool should have, or what you think that other tools lack is welcome. (send me in PM) Cheers, Jonathan -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
Re: Deploying Feature in manage.py
I agree with others that this is better left to tools such as fabric/cuisine as they are build to handle these kind of tasks: http://readthedocs.org/docs/fabric/en/latest/api/contrib/project.html -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/uwCmcgoVlKcJ. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
Re: Deploying Feature in manage.py
Having done deployments of varying scales and having spent a lot of time with Fabric, as well as some with Chef, Puppet, etc. I don't think there's any way we can build a tool that will meet any but the absolute simplest of needs without unnecessarily re-inventing a lot of wheels. However, if you're interested in pursuing this project then this is a great space for a 3rd-party app that ties in the features you'd like to see as management commands. There's absolutely no reason this needs to live in core and if it gains traction with the community then I could see it being a wonderfully useful asset. All the best, - Gabriel -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/uidNz6GYzn8J. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
Re: Deploying Feature in manage.py
On 23 oct. 2011, at 21:59, feel wrote: > Hi, I wanted to propose a new possible feature in Django project that > allows to sync the local folder with the remote one of the server > defining all the configuration directly in settings.py. Hi Filippo, I'm not convinced we can build a sufficiently useful and generic solution on this basis. For instance, many people prefer going through a (D)VCS rather than copying files directly between the development and production machines — it becomes necessary as soon as there's more than one developer. Furthermore, it's a different kind of program (systems administration, not web development) and there's no advantage to tie it to manage.py. For these reasons, it don't think it's a good idea to include this feature in Django. Standalone tools such as Fabric are designed just to address this problem space; you can probably find one that will suit your needs. Thanks for the suggestion anyway! -- Aymeric Augustin. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
