One of the hard parts about learning how to develop software is the minefield of acronyms that exists in the industry. The goal of this series of articles is to shine a light on an acronym so the next time another developer uses it in conversation you can follow along without missing a beat.
In this article, we’re going to be discussing the acronym LAMP. We’re picking this acronym because we’ve used it a couple of times in other articles and in doing so we have to use other acronyms which we’ll define in future articles. :-)
Read MoreWe’ve spent a lot of time discussing how to use Vagrant to create our development environment so now it’s time to bring everything we’ve learned together so we can finally develop some code.
Read MoreIn the past, if we want to have files that were accessible by the VM but could also be edited in an editor on the host we would have to clone the project into our VM, set up a shared directory, and then map the share in our host computer. Thankfully Vagrant allows us to easily tap into a feature know as synced folders that make this process so much easier.
Read MoreBecause the underlying technology Vagrant uses to create our development environment is the VM we can use the Secure Shell (or SSH) to administer our Unix based VMs. In this article, we’ll discuss how to use the built-in SSH tools of Vagrant.
Read MoreVagrant allows us several networking options for our development environments. In this article we’ll discuss making changes to our Vagrantfile to configure the networking.
Read MoreNow that we’ve learned how to manage the power state of our development environment we can discuss how we delete and reset our development environments using Vagrant commands.
Read MoreNow that we’ve created our Vagrantfile we can discuss how we manage the power state of our development environment using Vagrant commands.
Read Moresubscribe via RSS