On Thu, 13 Mar 2014 01:31:41 +0000, Gary Martin <[email protected]> wrote :
> On 12/03/14 10:47, Saint Germain wrote: > > Hello, > > > > I am currently working on an easy way to test/deploy Bloodhound > > based on Ansible + Vagrant. > > > > In theory we just have to do a "vagrant up" and the bloodhound > > website should be up and running in a VM. > > Or you can use directly the ansible-playbook on a real host to > > quickly build your website. > > > > I choose to work with Debian Wheezy + nginx + uWSGI > > > > I cannot give a deadline yet as I really don't know how long it will > > take me. But if other people are interested, we can share info on > > this subject. > > > > When it is ready it can perhaps be included in the trunk. > > > > Best regards, > > Hi, > > I thought that I should mention that I have recently looked at doing > something very similar. In my case I used salt rather than ansible and > using the apache2 webserver. I was going to see if I could redo it to > ansible as I assumed that vagrant would require the salty-vagrant > plugin. This is the main reason I didn't mention it earlier - I felt > that even the little extra effort involved in getting the plugin > installed on top of everything else might discourage people trying it. > Looking again I note that salt has been supported for a while. > > Anyway, definitely a good idea and well done for beating me to the > suggestion! > Hello Gary ! Some months ago I played a little with Salt as well after reading this: http://blog.gibbon.co/posts/2013-06-12-salting-your-django-stack.html Indeed I had some problem installing everything (had to delve into the Ruby world a little) but at the end everything worked quite well. Now I am repeating the experience with Ansible. Being a total beginner in this area, I cannot really talk about advantages/drawbacks of Salt vs Ansible. However I like the way Ansible is working (through SSH). I'll keep you updated ! Regards,
