Hello, I can't comment on best practices, since that can start a flamewar and feelings get hurts easily on what work good for one, or what works best/better/awesome
>From my point of view, the life cycle of the machines is short, and you are at 1 Vagrant destroy, vagrant up away of getting something again so, if I had to say what are the best practices, i will say: - be clean and tidy on the base boxes, if you get a new base box, be sure you are always using the last one - try to automate any change you require and make the scripts idempotent, that is, if they run twice do no harm. here, I have i been doing my scripts to check first and do after the check, and so far, pretty cool, i can do vagrant provision andi am 100% sure my hard disks won't be overwritten, my apps installation first check if the component is installed, it it's alreadym skip, if not install. so far I can instal an Oracle Rac with Virtualbox, totally hands free, and it's awesome for my job :) For developers, i think the best practice is setup a git for Vagrantfiles, and keep everything always clean.. not a developer, so I can't comment much here hope this helps! Alvaro. -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
