S
S
silentvick2014-01-04 15:50:19
Chef
silentvick, 2014-01-04 15:50:19

What is the best way to organize work with Vagrant and Chef?

I recently started using Vagrant in conjunction with Chef, and I had some questions in terms of organizing a workflow, storing cookbooks and transferring all this economy to other people (or self-access from different computers).
Suppose a team is working on a site whose code is stored in a git repository. With this, everything is clear. How in this case is it better to organize the transfer of vagrantfile, cookbooks, roles, etc.? Indeed, at the same time, cookbooks can be both from the official opscode repository (to download which you can simply use Berkshelf or Librarian and not drag the recipes themselves), or self-written ones (which are written locally for each project). For example, I wrote a vagrant config, set up roles, made a cookbook, and raised the machine. How to make it all available to others so that anyone can bring up exactly the same environment? Carry an archive with all the recipes and roles on a flash drive, or somehow involve git?
It will be interesting to know how you organize.

Answer the question

In order to leave comments, you need to log in

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question