Thanks Denis, I am not sure about using Gunicorn. Actually am thinking about a more async, non-blocking platform maybe using Tornado. What do you think?
Cheers, On 11 Dey, 1390, at 12:53 AM, Denis Darii wrote: > Hi Ashkan, > > You can take a look at our project: django-fagungis = DJANGO + FAbric + > GUnicorn + NGInx + Supervisor deployment > Here: https://bitbucket.org/DNX/django-fagungis/ > We use it for the same purpose as you described. > If you have some questions, suggestions or ideas about and for the project > feel free to open an issue on bitbucket. > > Happy new year to all! > > > On Sat, Dec 31, 2011 at 8:11 PM, Paul Msegeya <mseg...@gmail.com> wrote: > sounds good...Happy new year too. > > > On Sat, Dec 31, 2011 at 10:25 PM, Ashkan Roshanayi > <ashkan.roshan...@gmail.com> wrote: > Hi everybody, we are working in a geographically distributed agile team. I am > trying to design and configure our development environment and deployment > procedures and need to know about your valuable experiences. My requirements > are: > > * Each new developer can kick-start developing: dev environment and all > installs/configs (python related) should be achievable in 15 minutes. This > procedure should be automated and repeatable. > > * Everybody can pull & build whole project locally and run complete > *functional* test suite > > * Upon pushing code in our Github repo, it will be pulled out by our > build/staging server automatically --> all *functional* & *non-functional* > tests will be run by Jenkins --> if successful: we can test it manually on > this server too. > > * Admins can choose some features or profiles on this staging server and > deploy them to live (production) server by ideally executing a script > > > I've read a lot about virtualenv, pip, fabric, puppet, chef & blueprint and > used some of them but want to hear more about your recommendations, best > practices and potential pitfalls. Appreciate it very much. > > Happy new year :) > > -- > Ashkan > > -- > 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. > > > > -- > 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. > > > > -- > This e-mail and any file transmitted with it is intended only for the person > or entity to which is addressed and may contain information that is > privileged, confidential or otherwise protected from disclosure. Copying, > dissemination or use of this e-mail or the information herein by anyone other > than the intended recipient is prohibited. If you are not the intended > recipient, please notify the sender immediately by return e-mail, delete this > communication and destroy all copies. > > -- > 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. -- 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.
