Hello, Vagrant works with base boxes
it take a base box, and deploy a base box and then the plugin kicks in the dummy boxes is where everything is remote, thse dummy boxes they are just empty boxes with metadata.. they do nothing, they have nothing. depending on how you want to deliver/handle your project, some people want to create a vagrant box with specific metadata, but is just the metadata what's included. you can do it with include vagrantfile if your project can be shared as git or zip, then you can use the the dummy box and use the local vagrantfile for that hope this helps Alvaro. On Wed, Jun 10, 2015 at 10:59 AM, Guibin Tian <[email protected]> wrote: > Hello, > When we deploy to AWS with vagrant, we use the box dummy.box. My question is > what is this box? Because AWS is already virtual machine, if the dummy.box > is another layer of OS, that will be too much overhead. What is the > relationship between dummy.box and the AMI that will be chosen later? > > Thanks > > -- > 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. -- 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.
