Open lvnilesh opened 11 years ago
It worked when I added these lines to the chef-client
segment in Vagrantfile.
I wonder if there is a more elegant way.
chef.add_recipe "apt"
chef.add_recipe "build-essential"
chef.add_recipe "rbenv"
chef.add_recipe "ruby_build"
chef.add_recipe "nginx"
chef.add_recipe "unicorn"
chef.add_recipe "runit"
chef.add_recipe "ohai"
I'm not so familiar with Chef Server, but I'm digging in. If you remove the following two lines does it still work?
chef.add_recipe "runit"
chef.add_recipe "ohai"
I think I got the same thing and found that I need at least:
chef.add_recipe "apt"
chef.add_recipe "build-essential"
chef.add_recipe "rbenv"
chef.add_recipe "ruby_build"
Here are my findings:
uninitialized constant Chef::RubyBuild
@DanThiffault it may be a good idea to update README to include these 4 @smeyfroi suggested in run_list before using rails-lastmile.
I am also experimenting with adding capistrano style deployment directory layout as @claco suggests in his asesome blog posts at http://chrislaco.com/devops-toolbox
@lvnilesh I don't know if this is useful, but I definitely need those 4 when I'm building an EC2 instance using https://github.com/nrako/librarian-ec2 (chef-solo, not chef-server).
So in my case I don't need those 4 recipes to build a local vagrant/virtualbox, but I do when using librarian-ec2 to build an EC2 instance.
Not entirely sure why that might be the case, but anyway it does work on an EC2 with those recipes added into the mix. :-)
Just a note: I must add chef.add_recipe "nginx" to Vagrantfile in addition to @smeyfroi recipes...
This is the error I get when I edit Vagrantfile trying to get it working with
chef-server
My Vagrantfile edits trying to get it work with a
chef-server
I uploaded all needed cookbooks.
My working
chef-solo
segmentAny ideas where I am going wrong?