On Wed, Oct 7, 2015 at 2:17 AM, Krist Jin <[email protected]> wrote: > for me here. According to my understanding, what it does is to create a > bunch of same machine image for different platform (virtualbox, aws etc.) > from a single configuration
Hello, There is a way to import boxes in AWS, however I think is too complex, and I haven't used. So my suggestion was: - Using Vagrant, you should have 2 sets of task = Scripts that setup the base box = The Code you use. or application. Packer will help you to put into the base box the OS and those provisioning scripts. The advantage of this will be faster vagrant up, and that you can have multiple clouds base boxes. On top of this, you can have some release process that take the app/code, and will allow you to deploy this to a new box. This may sound overkill, but is where I see the process is going. So in your particular case, perhaps the best will be use the vagrant-aws plugin, and develop directly on AWS ? Thanks Alvaro. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0eyKAqsajCAGe%2BsRk-83imF4rKux3u0aJFH7tCcUL7uzhA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
