hdeshev
Joined 16 years ago
Joined 16 years ago
execute "#{virtualenv_dir}/bin/pip install -r #{requirements_file}" do user deploy_user group deploy_user end
IMO Chef shines when you have to move a lot of config files and generate node- and role-specific configs. I feel it's a lot simpler to just have recipe-specific files and templates packaged with the recipe and move them over with commands like cookbook_file and template.
Right now we are using both the technologies. Our stacks are Chef-based since we want people to be comfortable with reading (and possibly modifying) its code. We also reuse a lot of the Opscode recipes which simply do not exist for Fabric/Cuisine. Fabric and Cuisine have their place when we bootstrap a server and prepare the Chef environment and at several odd places where they keep things running together.
I'm all for server tweaking and I do it all the time, but sometimes it gets boring. I could probably do something better than configure php5-fpm for the thousandth time.
Right now, Stackful.io takes the pain from that when it comes to Node.js development. You just pick a server size and hit a button. 2 minutes later your machine is ready to rock and you can deploy your app with a simple Git push.
We are planning on doing the same for the other major web technologies. We have some pretty good progress with a Python stack and a PHP one is in our queue.
Yes, thanks to the websocket support that landed in recent Nginx releases.