Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
We are working on chef recipe that builds PHP from source. However, every time we make a change to our recipe and we want to run it again it takes a long time (about 20 minutes).
What we have been doing is making our changes then using:
vagrant destroy
followed by:
vagrant up
It would be nice if somehow we could just re-run our single recipe we are trying to update.
Anyone know how we could do this? Or how vagrant determines our php recipe is already installed/executed?
vagrant provisionshould do this for you. Chef should take care of only running the things that need to be run…like a changed recipe.