Thank you, yes. I would agree. I have am comfortable with Ansible and how it works. now I just need to put it all together. Per the above, i mentioned Packe ras well, not sure where that fits into the flow of what I am trying.
TY On Tuesday, July 14, 2020 at 3:08:32 PM UTC-7, Alexander Solla wrote: > > I'd say that the best practice is to pick some configuration management > system like Ansible, Salt, or Puppet that Vagrant supports, and use that to > keep your configuration files in version control. > > The idea would be to have Vagrant provision whatever system (Salt, etc) > you end up using, and then have that system (Salt, etc) provision the > configuration on your machine. > > On Tue, Jul 14, 2020 at 1:47 PM Jason Williams <[email protected] > <javascript:>> wrote: > >> hello everyone. >> I am starting to use Vagrant and Virtualbox more and more in my >> testing/development work. The more I work with the two, the more ideas and >> questions I have. I was hoping for some guidance/clarification and maybe >> best practices. >> Let me start with what I am working on and what I have done. >> >> I use NGINX quite a bit for web servers, proxying and load balancing. >> I have successfully setup a multi-vagrant setup using 2 servers to serve >> content. Step in the right direction. >> >> Where my question is really at is, once I spin up my Vagrant environment >> and start to do my testing, I see there are things that I need to change >> with the current boxes that I am using. >> This could be things like additional software, specific configuration >> file settings, copying over content etc. >> >> That all being said, is the best practices approach to then package up >> one of my current boxes which will contain all my changes? If that is true, >> what if I have I have different boxes in a multi-vagrant setup? Do i just >> package each one individually? >> Lastly, how do I call/use these new boxes that I have created? Do i need >> to edit the Vagrantfile and change the speciic image being used? >> >> This is where my rookiness to Vagrant is coming up short and was hoping >> the more experienced users could shed some light. >> >> I appreciate the help! >> >> Cheers! >> >> -- >> This mailing list is governed under the HashiCorp Community Guidelines - >> https://www.hashicorp.com/community-guidelines.html. Behavior in >> violation of those guidelines may result in your removal from this mailing >> list. >> >> GitHub Issues: https://github.com/hashicorp/vagrant/issues >> Discuss: https://discuss.hashicorp.com/c/vagrant/24 >> --- >> 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] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/vagrant-up/506a795d-30ce-4e4b-b384-22850e3aac91o%40googlegroups.com >> >> <https://groups.google.com/d/msgid/vagrant-up/506a795d-30ce-4e4b-b384-22850e3aac91o%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/hashicorp/vagrant/issues Discuss: https://discuss.hashicorp.com/c/vagrant/24 --- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/98bf52d1-ba71-4fc8-9007-98d0f06a65c7o%40googlegroups.com.
