Fixing "Works on my Machine" with Vagrant

Sign in to queue

Description

Join your guide Cory Fowler as he talks to the product teams in Redmond as well as the web community.

This week Cory goes solo to show you a great tool for working on different projects, or working with large teams, called Vagrant. Vagrant is a tool which helps you create and configure lightweight, reproducible, and portable development environments. Vagrant leverages virtualization technologies such as Virtual Box, VMWare Fusion/Workstation and Hyper-V to stand up development environments which are configured using a Vagrantfile and in some cases a provisioning script which can use AnsibleCFEngineChef, DockerPuppet or Salt.

In addition to the provisioners above the Hyper-V Provider for Windows adds the ability to provision your Windows boxes using Windows Remote Management (WinRM).

Show Notes

 

Embed

Download

The Discussion

  • User profile image
    rplaire

    Why not use WinRM which is now part of vagrant core instead of SSH (@ ~12:00)?

  • User profile image
    SyntaxC4

    @rplaire - I noticed that just after recording this show. Would like to hear if there is a preference amongst Vagrant users considering not all Of them run Windows.

  • User profile image
    Martin

    Very interesting, especially the part about Vagrant and Azure. Although, one question arose; Is it possible in some easy way to use your own Vagrant box(for example a dev environment) and set it as the Azure image instead of using the preconfigured ones?

  • User profile image
    SyntaxC4

    @Martin: There is current a bug listed in the vagrant-azure repository (https://github.com/MSOpenTech/vagrant-azure/issues/29) which is asking to use a precaptured image in Azure. This might be different from what you're asking, but it would be good to add an issue to see if it is something that would be considered by the MS Open Tech team.

  • User profile image
    Martin

    @SyntaxC4: Briliant, made a comment in that thread.

Add Your 2 Cents