Hi there
cool stuff.
Now the next step usually is measure that Vagrant up time, and see how much
of that can be done in the base box.
When you identify those steps, and you separate the provisioning, then you
can:
a - vagrant up upto the first step, vagrant package
vagrant up 2nd step and measure this time.
vagrant + virtualbox allow you package a vm, but not others
b. use packer to create a VM, or update an existing one upto the point
where the first provisioning part happen.
For Virtualbox and vmware you can start on an existing VM, so you can have
like a bake factory.
No need to over optimize what you got, just sharing what feels the natural
path when those vagrant up start feeling slow
:)
Alvaro
On Saturday, September 17, 2016 at 12:20:36 AM UTC+2, Edward Evans wrote:
>
> I tried the zip method and that worked great...thanks so much! I now have
> the machine getting added to the domain, installing Sql Server, attaching a
> database and adding all users and security. Awesome stuff.
>
--
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/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
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 vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vagrant-up/8bb2a9d2-c132-47af-8825-5d69dfda7551%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
