{"id":18803,"date":"2016-01-03T03:01:38","date_gmt":"2016-01-02T17:01:38","guid":{"rendered":"http:\/\/www.rjmprogramming.com.au\/ITblog\/?p=18803"},"modified":"2016-01-04T14:48:23","modified_gmt":"2016-01-04T04:48:23","slug":"vagrant-primer-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/vagrant-primer-tutorial\/","title":{"rendered":"Vagrant Primer Tutorial"},"content":{"rendered":"
\"Vagrant<\/a>

Vagrant Primer Tutorial<\/p><\/div>\n

In understanding what is out there on the net, tend to want to form relationships in my mind, between applications.<\/p>\n

So here’s a good one … VirtualBox<\/a> with Vagrant … or perhaps … VirtualMachine<\/a> with Vagrant.<\/p>\n

So here’s another one that’ll knock your socks off (and you’ll want to read after\/before\/same time\/while having corn flakes as today (to get it all in context, if this is new knowledge)) … Ansible<\/a> with Vagrant, that we talked about yesterday with Ansible Hello World Primer Tutorial<\/a> as shown below. As you read it, take note of the title of the book we recommend … “Ansible Up and Running” by Lorin Hochstein … the word “up” is bound to be in the list of a deployer’s favourite words, and is critical to all “Vagrant” talk as its favourite command (and its “nirvana” (if successful), and is slow the first time (when “vagrant up” is often preceded by an initialization vagrant command such as “vagrant init ubuntu\/trusty32”) with a project on an individual programmer’s system, but fast from then on for that programmer “revisiting”, so that on multiple projects they’re zooming (ie. cd’ing) around to places and going “vagrant up” vagrant up<\/font> vagrant up<\/font> vagrant up<\/font>) is …
\nvagrant up<\/code>
\n … and for today’s book recommendation … “Vagrant Up and Running” by Mitchell Hashimoto … fancy that?!\n<\/p>\n

So what’s Vagrant<\/a>? And why is it so friendly?<\/p>\n

Can try to answer the first now, but the second one relates to early times spent with Caspar the Ghost … but we digress.<\/p>\n

To quote the Vagrant landing page …<\/p>\n

\nCreate and configure lightweight, reproducible, and portable development environments.\n<\/p><\/blockquote>\n

What we understand in layperson’s terms is that if a client plonks a “system” on your doorstep and says any of …<\/p>\n

    \n
  1. “Fix this.”<\/li>\n
  2. “Maintain this.”<\/li>\n
  3. “Make it do this, now (awwwwwwwright … after lunch, then).”<\/li>\n<\/ol>\n

    … Vagrant may interface to an IDE like PHPStorm<\/a> (which we’ll talk about soon) or use Git (or GitHub) and\/or Composer in a Work Flow helping a group of team leaders and dbas and analysts and programmers achieve this by …<\/p>\n