Let’s get everything set up.
You need to take care of a couple of things before getting started.
Checking out the code¶
We need to check out the code and get it on your machine locally. Make sure you keep track of where you check out the code so that you can make changes to it.
git clone email@example.com:mpdavis/vinz.git
Our dev environment takes place inside of a VM thanks to Vagrant. You don’t have to pay much attention to this, because the code on your system is automatically synced to the right place in the VM. However, you do need to get the VM up and going before working.
The first thing we need to do is pull down the base box image to your machine. This is a VM image that vagrant can use in order to make VMs from.:
vagrant box add base http://files.vagrantup.com/precise64.box
On Windows, simply double-click run_vagrant.bat
This will take about a minute and a half depending on your machine and network connection. This creates the VM and installs everything needed in order to get it in a state that lets it run our code.
Developing on Vinz¶
At this point, the VM should be up and running. It already has a private network connection to your machine. You can see our application in a browser by going to http://10.13.37.2 The dev console will begin spitting out information related to the requests coming in.
If you edit the source code on the host machine, you can reload the webpage and see your changes.
This is simply written from memory. When (not if) you run into problems, let Michael know and he will update the README.