Lessons: 12Length: 40 minutes
- Overview
- Transcript
1.3 Advanced Setup: Vagrant and VMware
Vagrant supports many visualization providers. VMware is a popular and more powerful paid alternative to VirtualBox. In order to use VMware, you will need to install and activate its provider plugin. We’ll see how to do so in this lesson.
Related Links
1.Introduction
1.1Introduction01:16
1.2Installing VirtualBox and Vagrant02:05
1.3Advanced Setup: Vagrant and VMware02:42
2.Setting Up Your Node.js Stack
2.1Project Overview05:05
2.2The Vagrantfile05:02
2.3Installing Node.js Using NVM02:50
2.4Installing MongoDB and Redis05:43
2.5Node.js Development Workflow02:42
2.6Autostart the Node.js Application02:35
3.Exporting and Sharing
3.1Exporting and Sharing Your Vagrant Box07:28
3.2Sharing Your Local Vagrant Instance01:48
4.Conclusion
4.1Final Review00:54
1.3 Advanced Setup: Vagrant and VMware
Hi. Welcome back to Easy Node.js Development Environment with Vagrant. In this lesson, we'll be going through some additional steps to make VMWare play nicely with Vagrant. You might ask, Marcus, I already got VirtualBox, why would I need VMWare? The answer is easy, stability and performance. While VirtualBox is great for getting you started, VMware takes it up a notch and is the go to option for more demanding users. Now, both VMware and the Vagrant provider aren't free, you will have to purchase a license for each of them. VMware puts its desktop clients into two products. VMware Fusion runs on MacOS X while VMware Workstation is available for Windows and Linux. Because of that, there are also two different versions of the provider plugin. One for Fusion and another one for Workstation, so be aware which version you need for your environment. In this lesson, I will assume that you already installed and activated VMWare and that you have your Vagrant lessons file ready. First of all you need to install the provider. Vagrant offers a powerful plugin system to extend its core as much as you need it. There are many plugins adding support for different providers and provisioners like Puppet or Chef, as well networking plugins, or some for other more specialized purposes. I personally find it best to use as much of a [INAUDIBLE] station as possible. So your co-workers don't need to worry about cluttering up the systems with plugins or having some incompatible piece of software installed. It's just not error proof if you keep your customization inside the virtual machine. So to install the plugin, type vagrant plugin install and then either vagrant-vmware-Fusion or vagrant-vmware-workstation. This will install your plugin dependency. I'm on a Mac, so I'll use vagrant vmware-fusion. Next, we will need to activate the license. This can be done by typing vagrant plugin license, the name of your plugin, vagrant-vmware-fusion or vagrant-vmware-workstation and the path to your license file. Mine is in my home folder, so I'll just put the file name here. After you activated the license, you are ready to use VMWare to host your vagrant boxes. In the next lesson, I'll be giving you an overview about the project where you're going to use throughout the course and its dependencies. See you there!
