vagrant-packet 0.1.2 → 0.1.3

data/vendor/bundle/ruby/2.4.0/bundler/gems/vagrant-04f7215b5e3f/website/source/docs/vmware/vagrant-vmware-utility.html.md.erb

@@ -1,115 +0,0 @@
----
-layout: "docs"
-page_title: "Installation - VMware Provider"
-sidebar_current: "providers-vmware-utility"
-description: |-
-  The Vagrant VMware Utility works with the Vagrant VMware Provider to
-  interact with the system VMware installation.
----
-
-# Vagrant VMware Utility Installation
-
-## System Packages
-
-The Vagrant VMware Utility is provided as a system package. To install the
-utility, download and install the correct system package from the downloads
-page.
-
-<center>
-<a class="button" href="/vmware/downloads.html">Download <%= vmware_utility_version %></a>
-</center>
-
-## Manual Installation
-
-If there is no officially supported system package of the utility available,
-it may be possible to manually install utility. This applies to Linux platforms
-only. First, download the latest zip package from the releases page.
-
-Next create a directory for the executable and unpack the executable as
-root.
-
-```shell
-sudo mkdir /opt/vagrant-vmware-utility/bin
-sudo unzip -d /opt/vagrant-vmware-utility/bin vagrant-vmware-utility_1.0.0_x86_64.zip
-```
-
-After the executable has been installed, the utility setup tasks must be run. First,
-generate the required certificates:
-
-```shell
-sudo /opt/vagrant-vmware-utility/bin/vagrant-vmware-utility certificate generate
-```
-
-The path provided from this command can be used to set the [`utility_certificate_path`]
-(/docs/vmware/configuration.html#utility_certificate_path) in the Vagrantfile
-configuration if installing to a non-standard path.
-
-Finally, install the service. This will also enable the service.
-
-```shell
-sudo /usr/local/vagrant-vmware-utility/vagrant-vmware-utility service install
-```
-
-# Usage
-
-The Vagrant VMware Utility provides the Vagrant VMware provider plugin access
-to various VMware functionalities. The Vagrant VMware Utility is required by
-the Vagrant VMware Desktop provider plugin.
-
-## Vagrant VMware Utility Access
-
-The Vagrant VMware Utility provides support for all users on the system using
-the Vagrant VMware Desktop plugin. If access restrictions to the Utility need
-to be applied to users on the system, this can be accomplished by restricting
-user access to the certificates used for connecting to the service.
-
-On Windows platforms these certificates can be found at:
-
-* C:\ProgramData\HashiCorp\vagrant-vmware-desktop\certificates
-
-On POSIX platforms these certificates can be found at:
-
-* /opt/vagrant-vmware-desktop/certificates
-
-## Vagrant VMware Utility Service
-
-The Vagrant VMware Utility consists of a small service which runs on the
-host platform. When the utility installer package is installed, the service
-is configured to automatically start. If the plugin reports errors communicating
-with the service, it may have stopped for some reason. The most common cause of
-the service not being in a running state is the VMware application not being
-installed. The service can be started again by using the proper command below:
-
-### Windows
-
-On Windows platforms a service is created called `vagrant-vmware-utility`. The
-service can be manually started using the services GUI (`services.msc`) or by
-running the following command from a `cmd.exe` in administrator mode:
-
-```shell
-> net.exe start vagrant-vmware-utility
-```
-
-### macOS
-
-```shell
-> sudo launchctl load -w /Library/LaunchDaemons/com.vagrant.vagrant-vmware-utility.plist
-```
-
-### Linux systemd
-
-```shell
-> sudo systemctl start vagrant-vmware-utility
-```
-
-### Linux SysVinit
-
-```shell
-> sudo /etc/init.d/vagrant-vmware-utility start
-```
-
-### Linux runit
-
-```shell
-> sudo sv start vagrant-vmware-utility
-```

data/vendor/bundle/ruby/2.4.0/bundler/gems/vagrant-04f7215b5e3f/website/source/downloads.html.erb

@@ -1,62 +0,0 @@
----
-layout: "downloads"
-sidebar_current: "downloads"
-page_title: "Download"
-description: |-
-  This page lists all the available downloads for Vagrant.
----
-
-<h1>Download Vagrant</h1>
-
-<div class="downloads">
-  <div class="description row">
-    <div class="col-md-12">
-      <p>
-        Below are the available downloads for the latest version of Vagrant
-        (<%= latest_version %>). Please download the proper package for your
-        operating system and architecture.
-      </p>
-      <p>
-        You can find the
-        <a href="https://releases.hashicorp.com/vagrant/<%= latest_version %>/vagrant_<%= latest_version %>_SHA256SUMS">
-          SHA256 checksums for Vagrant <%= latest_version %>
-        </a>
-        online and you can
-        <a href="https://releases.hashicorp.com/vagrant/<%= latest_version %>/vagrant_<%= latest_version %>_SHA256SUMS.sig">
-          verify the checksum's signature file
-        </a>,
-        which has been signed using <a href="https://www.hashicorp.com/security.html" target="_blank" rel="nofollow noopener noreferrer">HashiCorp's GPG key</a>.
-        You can also <a href="https://releases.hashicorp.com/vagrant/" target="_blank" rel="nofollow noopener noreferrer">download older versions of Vagrant</a> from the releases service.
-      </p>
-      <p>
-        Check out the <a href="https://github.com/<%= github_slug %>/blob/v<%= latest_version %>/CHANGELOG.md">v<%= latest_version %> CHANGELOG</a> for information on the latest release.
-      </p>
-    </div>
-  </div>
-
-  <% product_versions.each do |os, arches| %>
-    <% next if os == "web" %>
-    <div class="row">
-      <div class="col-md-12 download">
-        <div class="icon pull-left"><%= system_icon(os) %></div>
-        <div class="details">
-          <h2 class="os-name"><%= pretty_os(os) %></h2>
-          <ul>
-            <% arches.each do |arch, url| %>
-              <li><a href="<%= url %>"><%= pretty_arch(arch) %></a></li>
-            <% end %>
-          </ul>
-          <div class="clearfix"></div>
-        </div>
-      </div>
-    </div>
-  <% end %>
-
-  <div class="row">
-    <div class="col-md-12 poweredby">
-      <a href="https://www.fastly.com?utm_source=hashicorp" target="_blank" rel="nofollow noopener noreferrer">
-        <%= inline_svg "fastly.svg", height: 50 %>
-      </a>
-    </div>
-  </div>
-</div>

data/vendor/bundle/ruby/2.4.0/bundler/gems/vagrant-04f7215b5e3f/website/source/index.html.erb

@@ -1,130 +0,0 @@
----
-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>
-          HashiCorp 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.4.0/bundler/gems/vagrant-04f7215b5e3f/website/source/intro/getting-started/boxes.html.md

@@ -1,119 +0,0 @@
----
-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.4.0/bundler/gems/vagrant-04f7215b5e3f/website/source/intro/getting-started/index.html.md

@@ -1,61 +0,0 @@
----
-layout: "intro"
-page_title: "Getting Started"
-sidebar_current: "gettingstarted"
-description: |-
-  The Vagrant getting started guide will walk you through your first
-  Vagrant project, and show off the basics of the major features Vagrant
-  has to offer.
----
-
-# Getting Started
-
-The Vagrant getting started guide will walk you through your first
-Vagrant project, and show off the basics of the major features Vagrant
-has to offer.
-
-If you are curious what benefits Vagrant has to offer, you
-should also read the ["Why Vagrant?"](/intro/index.html) page.
-
-The getting started guide will use Vagrant with [VirtualBox](https://www.virtualbox.org),
-since it is free, available on every major platform, and built-in to
-Vagrant. After reading the guide though, do not forget that Vagrant
-can work with [many other providers](/intro/getting-started/providers.html).
-
-Before diving into your first project, please [install the latest version of Vagrant](/docs/installation/).
-And because we will be using [VirtualBox](https://www.virtualbox.org) as our
-provider for the getting started guide, please install that as well.
-
-<div class="alert alert-block alert-info">
-  <strong>More of a book person?</strong> If you prefer to read a physical
-  book, you may be interested in
-  <a href="https://www.amazon.com/gp/product/1449335837/ref=as_li_qf_sp_asin_il_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1449335837&linkCode=as2&tag=vagrant-20" class="alert-link">
-  Vagrant: Up and Running</a>, written by the author of Vagrant and published by O'Reilly.
-</div>
-
-## Up and Running
-
-```
-$ vagrant init hashicorp/precise64
-$ vagrant up
-```
-
-After running the above two commands, you will have a fully running
-virtual machine in [VirtualBox](https://www.virtualbox.org) running
-Ubuntu 12.04 LTS 64-bit. You can SSH into this machine with
-`vagrant ssh`, and when you are done playing around, you can terminate the
-virtual machine with `vagrant destroy`.
-
-Now imagine every project you've ever worked on being this easy to
-set up! With Vagrant, `vagrant up` is all you need to work on any project,
-to install every dependency that project needs, and to set up any
-networking or synced folders, so you can continue working from the
-comfort of your own machine.
-
-The rest of this guide will walk you through setting up a more
-complete project, covering more features of Vagrant.
-
-## Next Steps
-
-You have just created your first virtual environment with Vagrant. Read on to
-learn more about [project setup](/intro/getting-started/project_setup.html).

data/vendor/bundle/ruby/2.4.0/bundler/gems/vagrant-04f7215b5e3f/website/source/intro/getting-started/install.html.md

@@ -1,55 +0,0 @@
----
-layout: "intro"
-page_title: "Install Vagrant - Getting Started"
-sidebar_current: "gettingstarted-install"
-description: |-
-  Installing Vagrant is extremely easy. Head over to the Vagrant downloads page
-  and get the appropriate installer or package for your platform. Install the
-  package using standard procedures for your operating system.
----
-
-# Install Vagrant
-
-Vagrant must first be installed on the machine you want to run it on. To make
-installation easy, Vagrant is distributed as a [binary package](/downloads.html)
-for all supported platforms and architectures. This page will not cover how to
-compile Vagrant from source, as that is covered in the
-[README](https://github.com/hashicorp/vagrant/blob/master/README.md) and is only
-recommended for advanced users.
-
-## Installing Vagrant
-
-To install Vagrant, first find the [appropriate package](/downloads.html) for
-your system and download it. Vagrant is packaged as an operating-specific
-package. Run the installer for your system. The installer will automatically add
-`vagrant` to your system path so that it is available in terminals. If it is not
-found, please try logging out and logging back in to your system (this is
-particularly necessary sometimes for Windows).
-
-## Verifying the Installation
-
-After installing Vagrant, verify the installation worked by opening a new command prompt or console, and checking that `vagrant` is available:
-
-```text
-$ vagrant
-Usage: vagrant [options] <command> [<args>]
-
-    -v, --version                    Print the version and exit.
-    -h, --help                       Print this help.
-
-# ...
-```
-
-## Caveats
-
-~> **Beware of system package managers!** Some operating system distributions
-include a vagrant package in their upstream package repos. Please do not install
-Vagrant in this manner. Typically these packages are missing dependencies or
-include very outdated versions of Vagrant. If you install via your system's
-package manager, it is very likely that you will experience issues. Please use
-the official installers on the downloads page.
-
-## Next Steps
-
-You have successfully downloaded and installed Vagrant! Read on to learn about
-[setting up your first Vagrant project](/intro/getting-started/project_setup.html).

data/vendor/bundle/ruby/2.4.0/bundler/gems/vagrant-04f7215b5e3f/website/source/intro/getting-started/networking.html.md

@@ -1,59 +0,0 @@
----
-layout: "intro"
-page_title: "Networking - Getting Started"
-sidebar_current: "gettingstarted-networking"
-description: |-
-  At this point we have a web server up and running with the ability to
-  modify files from our host and have them automatically synced to the guest.
-  However, accessing the web pages simply from the terminal from inside
-  the machine is not very satisfying. In this step, we will use Vagrant's
-  networking features to give us additional options for accessing the
-  machine from our host machine.
----
-
-# Networking
-
-At this point we have a web server up and running with the ability to
-modify files from our host and have them automatically synced to the guest.
-However, accessing the web pages simply from the terminal from inside
-the machine is not very satisfying. In this step, we will use Vagrant's
-_networking_ features to give us additional options for accessing the
-machine from our host machine.
-
-## Port Forwarding
-
-One option is to use _port forwarding_. Port forwarding allows you to
-specify ports on the guest machine to share via a port on the host machine.
-This allows you to access a port on your own machine, but actually have
-all the network traffic forwarded to a specific port on the guest machine.
-
-Let us setup a forwarded port so we can access Apache in our guest. Doing so
-is a simple edit to the Vagrantfile, which now looks like this:
-
-```ruby
-Vagrant.configure("2") do |config|
-  config.vm.box = "hashicorp/precise64"
-  config.vm.provision :shell, path: "bootstrap.sh"
-  config.vm.network :forwarded_port, guest: 80, host: 4567
-end
-```
-
-Run a `vagrant reload` or `vagrant up` (depending on if the machine
-is already running) so that these changes can take effect.
-
-Once the machine is running again, load `http://127.0.0.1:4567` in
-your browser. You should see a web page that is being served from
-the virtual machine that was automatically setup by Vagrant.
-
-## Other Networking
-
-Vagrant also has other forms of networking, allowing you to assign
-a static IP address to the guest machine, or to bridge the guest
-machine onto an existing network. If you are interested in other options,
-read the [networking](/docs/networking/) page.
-
-## Next Steps
-
-You have successfully configured networking for your virtual machine using
-Vagrant. Read on to learn about
-[setting up shares with Vagrant](/intro/getting-started/share.html).

data/vendor/bundle/ruby/2.4.0/bundler/gems/vagrant-04f7215b5e3f/website/source/intro/getting-started/project_setup.html.md

@@ -1,46 +0,0 @@
----
-layout: "intro"
-page_title: "Project Setup - Getting Started"
-sidebar_current: "gettingstarted-projectsetup"
-description: |-
-  The first step in configuring any Vagrant project is to create a Vagrantfile.
----
-
-# Project Setup
-
-The first step in configuring any Vagrant project is to create a
-[Vagrantfile](/docs/vagrantfile/). The purpose of the
-Vagrantfile is twofold:
-
-1. Mark the root directory of your project. Many of the configuration
-   options in Vagrant are relative to this root directory.
-
-2. Describe the kind of machine and resources you need to run your project,
-   as well as what software to install and how you want to access it.
-
-Vagrant has a built-in command for initializing a directory for usage
-with Vagrant: `vagrant init`. For the purpose of this getting started guide,
-please follow along in your terminal:
-
-```
-$ mkdir vagrant_getting_started
-$ cd vagrant_getting_started
-$ vagrant init
-```
-
-This will place a `Vagrantfile` in your current directory. You can
-take a look at the Vagrantfile if you want, it is filled with comments
-and examples. Do not be afraid if it looks intimidating, we will modify it
-soon enough.
-
-You can also run `vagrant init` in a pre-existing directory to
-set up Vagrant for an existing project.
-
-The Vagrantfile is meant to be committed to version control with
-your project, if you use version control. This way, every person working
-with that project can benefit from Vagrant without any upfront work.
-
-## Next Steps
-
-You have successfully created your first project environment. Read on to learn
-more about [Vagrant boxes](/intro/getting-started/boxes.html).