<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Portable on Janik von Rotz</title>
    <link>https://janikvonrotz.ch/tags/portable/</link>
    <description>Recent content in Portable on Janik von Rotz</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Tue, 02 Jul 2013 11:54:35 +0000</lastBuildDate>
    <atom:link href="https://janikvonrotz.ch/tags/portable/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Vagrant - portable development environment</title>
      <link>https://janikvonrotz.ch/2013/07/02/vagrant-portable-development-environment/</link>
      <pubDate>Tue, 02 Jul 2013 11:54:35 +0000</pubDate>
      <guid>https://janikvonrotz.ch/2013/07/02/vagrant-portable-development-environment/</guid>
      <description>&lt;p&gt;Today almost every coder uses git or another vcs and a related service like github for code hosting.&lt;/p&gt;&#xA;&lt;p&gt;As a front end designer twitters bower is the right tool to manage your libary dependencies.&lt;/p&gt;&#xA;&lt;p&gt;And for the backend developer the npm package manager is always on board.&lt;/p&gt;&#xA;&lt;p&gt;Those tools have changed the way of developing websites and webapplication.&lt;/p&gt;&#xA;&lt;p&gt;They&amp;rsquo;ve increased productivity and the flexibilty for your application.&lt;/p&gt;&#xA;&lt;p&gt;So far, there&amp;rsquo;s only one part lagging behind: It&amp;rsquo;s the development environment.&lt;/p&gt;&#xA;&lt;p&gt;And yes, also for this part exists a solution. I&amp;rsquo;m talking about &lt;!-- raw HTML omitted --&gt;vagrant&lt;!-- raw HTML omitted --&gt;&lt;/p&gt;&#xA;&lt;p&gt;It is the lost child in my development workflow, it&amp;rsquo;s the perfect supplement.&lt;/p&gt;&#xA;&lt;p&gt;With vagrant and vm provider of your choice (virtualbox, vmware or amazon so far) you&amp;rsquo;re abble to setup a portable and reproducible development environment. Vargant installs a virtual machine based on virtual appliance, by default vargant syncs your folder with the virtual machines default directory. With this setup you are able to run your code in virtual machine but still code your stuff as it appeals to you on your local host.&lt;/p&gt;&#xA;&lt;p&gt;Well, that looks interesting, where should I start? For newbies the offical documentation should be fine: &lt;!-- raw HTML omitted --&gt;&lt;a href=&#34;https://docs.vagrantup.com/v2/getting-started/index.html&#34;&gt;https://docs.vagrantup.com/v2/getting-started/index.html&lt;/a&gt;&lt;!-- raw HTML omitted --&gt;&lt;/p&gt;&#xA;&lt;p&gt;Follow step by step and you&amp;rsquo;ll run a virtual linux appliance with an apache preinstalled.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
