vagrant-aws-mkubenka 0.7.2.pre.14 → 0.7.2.pre.16

data/vendor/bundle/ruby/2.3.0/bundler/gems/vagrant-1ee58c40e3f5/website/source/index.html.erb

@@ -0,0 +1,130 @@
+---
+description: |-
+  Vagrant enables users to create and configure lightweight, reproducible, and
+  portable development environments.
+---
+
+<header>
+  <div class="container hero">
+    <div class="row">
+      <div class="col-md-offset-2 col-md-8">
+        <%= inline_svg "logo-hashicorp.svg", height: 120, class: "logo" %>
+
+        <h1>Development Environments Made Easy</h1>
+
+        <a class="button primary" href="/intro/index.html">Get Started</a>
+        <a class="button" href="/downloads.html">Download <%= latest_version %></a>
+        <a class="button" href="https://app.vagrantup.com/boxes/search" target="_TOP">Find Boxes</a>
+      </div>
+    </div>
+  </div>
+</header>
+
+<section id="simple" class="marketing blue">
+  <div class="container">
+    <div class="row">
+      <div class="col-md-6">
+        <span class="callout">Unified Workflow</span>
+        <h2>Simple and Powerful</h2>
+        <p>
+          Vagrant provides the same, easy workflow regardless of your role as
+          a developer, operator, or designer. It leverages a declarative
+          configuration file which describes all your software requirements,
+          packages, operating system configuration, users, and more.
+        </p>
+      </div>
+      <div class="col-md-6">
+        <div class="terminal">
+          <span class="circle"></span>
+          <span class="circle"></span>
+          <span class="circle"></span>
+          <div class="terminal-content">
+            <span class="command">$ vagrant init hashicorp/precise64</span>
+            <span>&nbsp;</span>
+            <span class="command">$ vagrant up</span>
+            <span>Bringing machine 'default' up with 'virtualbox' provider...</span>
+            <span>==> default: Importing base box 'hashicorp/precise64'...</span>
+            <span>==> default: Forwarding ports...</span>
+            <span>    default: 22 (guest) => 2222 (host) (adapter 1)</span>
+            <span>==> default: Waiting for machine to boot...</span>
+            <span>&nbsp;</span>
+            <span class="command">$ vagrant ssh</span>
+            <span>vagrant@precise64:~$ _</span>
+          </div>
+        </div>
+      </div>
+    </div>
+  </div>
+</section>
+
+<section id="parity" class="marketing">
+  <div class="container">
+    <div class="row">
+      <div class="col-md-6">
+        <div class="parity-image">
+          <%= inline_svg "parity.svg" %>
+        </div>
+      </div>
+      <div class="col-md-6">
+        <span class="callout">Enforce Consistency</span>
+        <h2>Production Parity</h2>
+        <p>
+          The cost of fixing a bug exponentially increases the closer it gets to
+          production. Vagrant aims to mirror production environments by
+          providing the same operating system, packages, users, and
+          configurations, all while giving users the flexibility to use their
+          favorite editor, IDE, and browser. Vagrant also integrates with your
+          existing configuration management tooling like Chef, Puppet, Ansible,
+          or Salt, so you can use the same scripts to configure Vagrant as
+          production.
+        </p>
+      </div>
+    </div>
+  </div>
+</section>
+
+<section id="cross" class="marketing blue-dark">
+  <div class="container">
+    <div class="row">
+      <div class="col-md-6">
+        <span class="callout">Cross-Platform</span>
+        <h2>Works where you work</h2>
+        <p>
+          Vagrant works on Mac, Linux, Windows, and more. Remote development
+          environments force users to give up their favorite editors and
+          programs. Vagrant works on your local system with the tools you're
+          already familiar with. Easily code in your favorite text editor, edit
+          images in your favorite manipulation program, and debug using your
+          favorite tools, all from the comfort of your local laptop.
+        </p>
+      </div>
+      <div class="col-md-6">
+        <div class="systems">
+          <%= inline_svg "systems/apple.svg" %>
+          <%= inline_svg "systems/linux.svg" %>
+          <%= inline_svg "systems/windows.svg" %>
+        </div>
+      </div>
+    </div>
+  </div>
+</section>
+
+<section id="trusted" class="marketing black">
+  <div class="container">
+    <div class="row">
+      <div class="col-xs-12">
+        <span class="callout">Trusted at Scale</span>
+        <h2>Trusted By</h2>
+        <p>
+          Vagrant is trusted by thousands of developers, operators, and
+          designers everyday. Here are just a few of the organizations that
+          choose Vagrant to automate their development environments, in
+          lightweight and reproducible ways.
+        </p>
+        <p class="logos">
+          <%= image_tag "customers.png", alt: "customers" %>
+        </p>
+      </div>
+    </div>
+  </div>
+</section>

data/vendor/bundle/ruby/2.3.0/bundler/gems/vagrant-1ee58c40e3f5/website/source/intro/getting-started/boxes.html.md

@@ -0,0 +1,119 @@
+---
+layout: "intro"
+page_title: "Boxes - Getting Started"
+sidebar_current: "gettingstarted-boxes"
+description: |-
+  Instead of building a virtual machine from scratch, which would be a
+  slow and tedious process, Vagrant uses a base image to quickly clone
+  a virtual machine. These base images are known as "boxes" in Vagrant,
+  and specifying the box to use for your Vagrant environment is always
+  the first step after creating a new Vagrantfile.
+---
+
+# Boxes
+
+Instead of building a virtual machine from scratch, which would be a
+slow and tedious process, Vagrant uses a base image to quickly clone
+a virtual machine. These base images are known as "boxes" in Vagrant,
+and specifying the box to use for your Vagrant environment is always
+the first step after creating a new Vagrantfile.
+
+## Installing a Box
+
+If you ran the commands on the [getting started overview page](/intro/getting-started/),
+then you've already installed a box before, and you do not need to run
+the commands below again. However, it is still worth reading this section
+to learn more about how boxes are managed.
+
+Boxes are added to Vagrant with `vagrant box add`. This stores the box
+under a specific name so that multiple Vagrant environments can re-use it.
+If you have not added a box yet, you can do so now:
+
+```
+$ vagrant box add hashicorp/precise64
+```
+
+This will download the box named "hashicorp/precise64" from
+[HashiCorp's Vagrant Cloud box catalog](https://vagrantcloud.com/boxes/search), a place where you can find
+and host boxes. While it is easiest to download boxes from HashiCorp's Vagrant Cloud
+you can also add boxes from a local file, custom URL, etc.
+
+Boxes are globally stored for the current user. Each project uses a box
+as an initial image to clone from, and never modifies the actual base
+image. This means that if you have two projects both using the `hashicorp/precise64`
+box we just added, adding files in one guest machine will have no effect
+on the other machine.
+
+In the above command, you will notice that boxes are namespaced. Boxes are
+broken down into two parts - the username and the box name - separated by a
+slash. In the example above, the username is "hashicorp", and the box is
+"precise64". You can also specify boxes via URLs or local file paths, but that
+will not be covered in the getting started guide.
+
+~> **Namespaces do not guarantee canonical boxes!** A common misconception is
+that a namespace like "ubuntu" represents the canonical space for Ubuntu boxes.
+This is untrue. Namespaces on Vagrant Cloud behave very similarly to namespaces on
+GitHub, for example. Just as GitHub's support team is unable to assist with
+issues in someone's repository, HashiCorp's support team is unable to assist
+with third-party published boxes.
+
+## Using a Box
+
+Now that the box has been added to Vagrant, we need to configure our
+project to use it as a base. Open the `Vagrantfile` and change the
+contents to the following:
+
+```ruby
+Vagrant.configure("2") do |config|
+  config.vm.box = "hashicorp/precise64"
+end
+```
+
+The "hashicorp/precise64" in this case must match the name you used to add
+the box above. This is how Vagrant knows what box to use. If the box was not
+added before, Vagrant will automatically download and add the box when it is
+run.
+
+You may specify an explicit version of a box by specifying `config.vm.box_version`
+for example:
+
+```ruby
+Vagrant.configure("2") do |config|
+  config.vm.box = "hashicorp/precise64"
+  config.vm.box_version = "1.1.0"
+end
+```
+
+You may also specify the URL to a box directly using `config.vm.box_url`:
+
+```ruby
+Vagrant.configure("2") do |config|
+  config.vm.box = "hashicorp/precise64"
+  config.vm.box_url = "http://files.vagrantup.com/precise64.box"
+end
+```
+
+In the next section, we will bring up the Vagrant environment and interact
+with it a little bit.
+
+## Finding More Boxes
+
+For the remainder of this getting started guide, we will only use the
+"hashicorp/precise64" box we added previously. But soon after finishing
+this getting started guide, the first question you will probably have is
+"where do I find more boxes?"
+
+The best place to find more boxes is [HashiCorp's Vagrant Cloud box catalog](https://vagrantcloud.com/boxes/search).
+HashiCorp's Vagrant Cloud has a public directory of freely available boxes that
+run various platforms and technologies. HashiCorp's Vagrant Cloud also has a great search
+feature to allow you to find the box you care about.
+
+In addition to finding free boxes, HashiCorp's Vagrant Cloud lets you host your own
+boxes, as well as private boxes if you intend on creating boxes for your
+own organization.
+
+## Next Steps
+
+You have successfully downloaded your first Vagrant box and configured the
+Vagrantfile to utilize that box. Read on to learn about [bringing up and access
+the Vagrant machine via SSH](/intro/getting-started/up.html).

data/vendor/bundle/ruby/2.3.0/bundler/gems/vagrant-1ee58c40e3f5/website/source/intro/getting-started/share.html.md

@@ -0,0 +1,57 @@
+---
+layout: "intro"
+page_title: "Share - Getting Started"
+sidebar_current: "gettingstarted-share"
+description: |-
+  Now that we have a web server up and running and accessible from your machine,
+  we have a fairly functional development environment. But in addition to
+  providing a development environment, Vagrant also makes it easy to share
+  and collaborate on these environments. The primary feature to do this in
+  Vagrant is called Vagrant Share.
+---
+
+# Share
+
+Now that we have a web server up and running and accessible from your machine,
+we have a fairly functional development environment. But in addition to
+providing a development environment, Vagrant also makes it easy to share
+and collaborate on these environments. The primary feature to do this in
+Vagrant is called [Vagrant Share](/docs/share/).
+
+Vagrant Share lets you share your Vagrant environment to anyone around the
+world with an Internet connection. It will give you a URL that will route
+directly to your Vagrant environment from any device in the world that is
+connected to the Internet.
+
+Run `vagrant share`:
+
+```
+$ vagrant share
+...
+==> default: Creating Vagrant Share session...
+==> default: HTTP URL: http://b1fb1f3f.ngrok.io
+...
+```
+
+Your URL will be different, so do not try the URL above. Instead, copy
+the URL that `vagrant share` outputted for you and visit that in a web
+browser. It should load the Apache page we setup earlier.
+
+If you modify the files in your shared folder and refresh the URL, you will
+see it update! The URL is routing directly into your Vagrant environment,
+and works from any device in the world that is connected to the internet.
+
+To end the sharing session, hit `Ctrl+C` in your terminal. You can refresh
+the URL again to verify that your environment is no longer being shared.
+
+Vagrant Share is much more powerful than simply HTTP sharing. For more
+details, see the [complete Vagrant Share documentation](/docs/share/).
+
+~> **Vagrant share is not designed to serve production traffic!** Please do not
+rely on Vagrant share outside of development or Q/A. The Vagrant share service
+is not designed to carry production-level traffic.
+
+## Next Steps
+
+You have successfully shared your environment with the world. Congratulations!
+Read on to learn about the [teardown process](/intro/getting-started/teardown.html).

data/vendor/bundle/ruby/2.3.0/bundler/gems/vagrant-1ee58c40e3f5/website/source/intro/vs/docker.html.md

@@ -0,0 +1,34 @@
+---
+layout: "intro"
+page_title: "Vagrant vs. Docker"
+sidebar_current: "vs-docker"
+description: |-
+  Vagrant and Docker both provide isolation primitives. This page details the
+  differences between them.
+---
+
+# Vagrant vs. Docker
+
+Vagrant is a tool focused on providing a consistent development environment
+workflow across multiple operation systems. Docker is a container management
+that can consistently run software as long as a containerization system exists.
+
+Containers are generally more lightweight than virtual machines, so starting
+and stopping containers is extremely fast. Most common development machines
+don't have a containerization system built-in, and Docker uses a virtual machine
+with Linux installed to provide that.
+
+Currently, Docker lacks support for certain operating systems (such as
+BSD). If your target deployment is one of these operating systems,
+Docker will not provide the same production parity as a tool like Vagrant.
+Vagrant will allow you to run a Windows development environment on Mac or Linux,
+as well.
+
+For microservice heavy environments, Docker can be attractive because you
+can easily start a single Docker VM and start many containers above that
+very quickly. This is a good use case for Docker. Vagrant can do this as well
+with the Docker provider. A primary benefit for Vagrant is a consistent workflow
+but there are many cases where a pure-Docker workflow does make sense.
+
+Both Vagrant and Docker have a vast library of community-contributed "images"
+or "boxes" to choose from.