vagrant-packet 0.1.2 → 0.1.3

data/vendor/bundle/ruby/2.3.0/bundler/gems/vagrant-04f7215b5e3f/website/source/docs/cli/aliases.html.md

@@ -1,74 +0,0 @@
----
-layout: "docs"
-page_title: "Aliases - Command-Line Interface"
-sidebar_current: "cli-aliases"
-description: |-
-  Custom Vagrant commands can be defined using aliases, allowing for a simpler,
-  easier, and more familiar command line interface.
----
-
-# Aliases
-
-Inspired in part by Git's own
-[alias functionality](https://git-scm.com/book/en/v2/Git-Basics-Git-Aliases),
-aliases make your Vagrant experience simpler, easier, and more familiar by
-allowing you to create your own custom Vagrant commands.
-
-Aliases can be defined within `VAGRANT_HOME/aliases` file, or in a custom file
-defined using the `VAGRANT_ALIAS_FILE` environment variable, in the following
-format:
-
-```
-# basic command-level aliases
-start = up
-stop = halt
-
-# advanced command-line aliases
-eradicate = !vagrant destroy && rm -rf .vagrant
-```
-
-In a nutshell, aliases are defined using a standard `key = value` format, where
-the `key` is the new Vagrant command, and the `value` is the aliased command.
-Using this format, there are two types of aliases that can be defined: internal
-and external aliases.
-
-## Internal Aliases
-
-Internal command aliases call the CLI class directly, allowing you to alias
-one Vagrant command to another Vagrant command. This technique can be very
-useful for creating commands that you think _should_ exist. For example,
-if `vagrant stop` feels more intuitive than `vagrant halt`, the following alias
-definitions would make that change possible:
-
-```
-stop = halt
-```
-
-This makes the following commands equivalent:
-
-```
-vagrant stop
-vagrant halt
-```
-
-## External Aliases
-
-While internal aliases can be used to define more intuitive Vagrant commands,
-external command aliases are used to define Vagrant commands with brand new
-functionality. These aliases are prefixed with the `!` character, which
-indicates to the interpreter that the alias should be executed as a shell
-command. For example, let's say that you want to be able to view the processor
-and memory utilization of the active project's virtual machine. To do this, you
-could define a `vagrant metrics` command that returns the required information
-in an easy-to-read format, like so:
-
-```
-metrics = !ps aux | grep "[V]BoxHeadless" | grep $(cat .vagrant/machines/default/virtualbox/id) | awk '{ printf("CPU: %.02f%%, Memory: %.02f%%", $3, $4) }'
-```
-
-The above alias, from within the context of an active Vagrant project, would
-print the CPU and memory utilization directly to the console:
-
-```
-CPU: 4.20%, Memory: 11.00%
-```

data/vendor/bundle/ruby/2.3.0/bundler/gems/vagrant-04f7215b5e3f/website/source/docs/cli/box.html.md

@@ -1,205 +0,0 @@
----
-layout: "docs"
-page_title: "vagrant box - Command-Line Interface"
-sidebar_current: "cli-box"
-description: |-
-  The "vagrant box" command is used to manage "vagrant box add", "vagrant box
-  remove", and other box-related commands such as "outdated", "list", and
-  "update".
----
-
-# Box
-
-**Command: `vagrant box`**
-
-This is the command used to manage (add, remove, etc.) [boxes](/docs/boxes.html).
-
-The main functionality of this command is exposed via even more subcommands:
-
-* [`add`](#box-add)
-* [`list`](#box-list)
-* [`outdated`](#box-outdated)
-* [`prune`](#box-prune)
-* [`remove`](#box-remove)
-* [`repackage`](#box-repackage)
-* [`update`](#box-update)
-
-# Box Add
-
-**Command: `vagrant box add ADDRESS`**
-
-This adds a box with the given address to Vagrant. The address can be
-one of three things:
-
-* A shorthand name from the
-[public catalog of available Vagrant images](https://vagrantcloud.com/boxes/search),
-such as "hashicorp/precise64".
-
-* File path or HTTP URL to a box in a [catalog](https://vagrantcloud.com/boxes/search).
-For HTTP, basic authentication is supported and `http_proxy` environmental
-variables are respected. HTTPS is also supported.
-
-* URL directly a box file. In this case, you must specify a `--name` flag
-(see below) and versioning/updates will not work.
-
-If an error occurs during the download or the download is interrupted with
-a Ctrl-C, then Vagrant will attempt to resume the download the next time it
-is requested. Vagrant will only attempt to resume a download for 24 hours
-after the initial download.
-
-## Options
-
-* `--box-version VALUE` - The version of the box you want to add. By default,
-  the latest version will be added. The value of this can be an exact version
-  number such as "1.2.3" or it can be a set of version constraints. A version
-  constraint looks like ">= 1.0, < 2.0".
-
-* `--cacert CERTFILE` - The certificate for the CA used to verify the peer.
-  This should be used if the remote end does not use a standard root CA.
-
-* `--capath CERTDIR` - The certificate directory for the CA used to verify the peer.
-  This should be used if the remote end does not use a standard root CA.
-
-* `--cert CERTFILE` - A client certificate to use when downloading the box, if
-  necessary.
-
-* `--clean` - If given, Vagrant will remove any old temporary files from
-  prior downloads of the same URL. This is useful if you do not want Vagrant
-  to resume a download from a previous point, perhaps because the contents
-  changed.
-
-* `--force` - When present, the box will be downloaded and overwrite any
-  existing box with this name.
-
-* `--insecure` - When present, SSL certificates will not be verified if the
-  URL is an HTTPS URL.
-
-* `--provider PROVIDER` - If given, Vagrant will verify the box you are
-  adding is for the given provider. By default, Vagrant automatically
-  detects the proper provider to use.
-
-## Options for direct box files
-
-The options below only apply if you are adding a box file directly (when
-you are not using a catalog).
-
-* `--checksum VALUE` - A checksum for the box that is downloaded. If specified,
-  Vagrant will compare this checksum to what is actually downloaded and will
-  error if the checksums do not match. This is highly recommended since
-  box files are so large. If this is specified, `--checksum-type` must
-  also be specified. If you are downloading from a catalog, the checksum is
-  included within the catalog entry.
-
-* `--checksum-type TYPE` - The type of checksum that `--checksum` is if it
-  is specified. Supported values are currently "md5", "sha1", and "sha256".
-
-* `--name VALUE` - Logical name for the box. This is the value that you
-  would put into `config.vm.box` in your Vagrantfile. When adding a box from
-  a catalog, the name is included in the catalog entry and does not have
-  to be specified.
-
-<div class="alert alert-warning">
-  <strong>Checksums for versioned boxes or boxes from HashiCorp's Vagrant Cloud:</strong>
-  For boxes from HashiCorp's Vagrant Cloud, the checksums are embedded in the metadata
-  of the box. The metadata itself is served over TLS and its format is validated.
-</div>
-
-# Box List
-
-**Command: `vagrant box list`**
-
-This command lists all the boxes that are installed into Vagrant.
-
-# Box Outdated
-
-**Command: `vagrant box outdated`**
-
-This command tells you whether or not the box you are using in
-your current Vagrant environment is outdated. If the `--global` flag
-is present, every installed box will be checked for updates.
-
-Checking for updates involves refreshing the metadata associated with
-a box. This generally requires an internet connection.
-
-## Options
-
-* `--global` - Check for updates for all installed boxes, not just the
-  boxes for the current Vagrant environment.
-
-# Box Prune
-
-**Command: `vagrant box prune`**
-
-This command removes old versions of installed boxes. If the box is currently in use vagrant will ask for confirmation.
-
-## Options
-
-* `--provider PROVIDER` - The specific provider type for the boxes to destroy.
-
-* `--dry-run` - Only print the boxes that would be removed.
-
-* `--name NAME` - The specific box name to check for outdated versions.
-
-* `--force` - Destroy without confirmation even when box is in use.
-
-# Box Remove
-
-**Command: `vagrant box remove NAME`**
-
-This command removes a box from Vagrant that matches the given name.
-
-If a box has multiple providers, the exact provider must be specified
-with the `--provider` flag. If a box has multiple versions, you can select
-what versions to delete with the `--box-version` flag or remove all versions
-with the `--all` flag.
-
-## Options
-
-* `--box-version VALUE` - Version of version constraints of the boxes to
-  remove. See documentation on this flag for `box add` for more details.
-
-* `--all` - Remove all available versions of a box.
-
-* `--force` - Forces removing the box even if an active Vagrant
-  environment is using it.
-
-* `--provider VALUE` - The provider-specific box to remove with the given
-  name. This is only required if a box is backed by multiple providers.
-  If there is only a single provider, Vagrant will default to removing it.
-
-# Box Repackage
-
-**Command: `vagrant box repackage NAME PROVIDER VERSION`**
-
-This command repackages the given box and puts it in the current
-directory so you can redistribute it. The name, provider, and version
-of the box can be retrieved using `vagrant box list`.
-
-When you add a box, Vagrant unpacks it and stores it internally. The
-original `*.box` file is not preserved. This command is useful for
-reclaiming a `*.box` file from an installed Vagrant box.
-
-# Box Update
-
-**Command: `vagrant box update`**
-
-This command updates the box for the current Vagrant environment if there
-are updates available. The command can also update a specific box (outside
-of an active Vagrant environment), by specifying the `--box` flag.
-
-<small><i>Note that updating the box will not update an already-running Vagrant
-machine. To reflect the changes in the box, you will have to destroy and
-bring back up the Vagrant machine.</i></small>
-
-If you just want to check if there are updates available, use the
-`vagrant box outdated` command.
-
-## Options
-
-* `--box VALUE` - Name of a specific box to update. If this flag is not
-  specified, Vagrant will update the boxes for the active Vagrant
-  environment.
-
-* `--provider VALUE` - When `--box` is present, this controls what
-  provider-specific box to update. This is not required unless the box has
-  multiple providers. Without the `--box` flag, this has no effect.

data/vendor/bundle/ruby/2.3.0/bundler/gems/vagrant-04f7215b5e3f/website/source/docs/cli/connect.html.md

@@ -1,34 +0,0 @@
----
-layout: "docs"
-page_title: "vagrant connect - Command-Line Interface"
-sidebar_current: "cli-connect"
-description: |-
-  The "vagrant connect" command compliments the "vagrant share" command to allow
-  a user to remotely connect to your Vagrant environment.
----
-
-# Connect
-
-**Command: `vagrant connect NAME`**
-
-The connect command complements the
-[share command](/docs/cli/share.html) by enabling access to shared
-environments. You can learn about all the details of Vagrant Share in the
-[Vagrant Share section](/docs/share/).
-
-The reference of available command-line flags to this command
-is available below.
-
-## Options
-
-* `--disable-static-ip` - The connect command will not spin up a small
-  virtual machine to create a static IP you can access. When this flag is
-  set, the only way to access the connection is to use the SOCKS proxy
-  address outputted.
-
-* `--static-ip IP` - Tells connect what static IP address to use for the virtual
-  machine. By default, Vagrant connect will use an IP address that looks
-  available in the 172.16.0.0/16 space.
-
-* `--ssh` - Connects via SSH to an environment shared with
-  `vagrant share --ssh`.

data/vendor/bundle/ruby/2.3.0/bundler/gems/vagrant-04f7215b5e3f/website/source/docs/cli/destroy.html.md

@@ -1,41 +0,0 @@
----
-layout: "docs"
-page_title: "vagrant destroy - Command-Line Interface"
-sidebar_current: "cli-destroy"
-description: |-
-  The "vagrant destroy" command is used to stop the running virtual machine and
-  terminate use of all resources that were in use by that machine.
----
-
-# Destroy
-
-**Command: `vagrant destroy [name|id]`**
-
-This command stops the running machine Vagrant is managing and
-destroys all resources that were created during the machine creation process.
-After running this command, your computer should be left at a clean state,
-as if you never created the guest machine in the first place.
-
-For linux-based guests, Vagrant uses the `shutdown` command to gracefully
-terminate the machine. Due to the varying nature of operating systems, the
-`shutdown` command may exist at many different locations in the guest's `$PATH`.
-It is the guest machine's responsibility to properly populate the `$PATH` with
-directory containing the `shutdown` command.
-
-## Options
-
-* `-f` or `--force` - Do not ask for confirmation before destroying.
-* `--[no-]parallel` - Destroys multiple machines in parallel if the provider
-  supports it. Please consult the provider documentation to see if this feature
-  is supported.
-
-<div class="alert alert-info">
-  The `destroy` command does not remove a box that may have been installed on
-  your computer during `vagrant up`. Thus, even if you run `vagrant destroy`,
-  the box installed in the system will still be present on the hard drive. To
-  return your computer to the state as it was before `vagrant up` command, you
-  need to use `vagrant box remove`.
-
-  For more information, read about the
-  <a href="/docs/cli/box.html">`vagrant box remove`</a> command.
-</div>

data/vendor/bundle/ruby/2.3.0/bundler/gems/vagrant-04f7215b5e3f/website/source/docs/cli/global-status.html.md

@@ -1,39 +0,0 @@
----
-layout: "docs"
-page_title: "vagrant global-status - Command-Line Interface"
-sidebar_current: "cli-globalstatus"
-description: |-
-  The "vagrant global-status" command is used to determine the state of all
-  active Vagrant environments on the system for the currently logged in user.
----
-
-# Global Status
-
-**Command: `vagrant global-status`**
-
-This command will tell you the state of all active Vagrant environments
-on the system for the currently logged in user.
-
-~> **This command does not actively verify the state of machines**,
-and is instead based on a cache. Because of this, it is possible to see
-stale results (machines say they're running but they're not). For example,
-if you restart your computer, Vagrant would not know. To prune the invalid
-entries, run global status with the `--prune` flag.
-
-The IDs in the output that look like `a1b2c3` can be used to control
-the Vagrant machine from anywhere on the system. Any Vagrant command
-that takes a target machine (such as `up`, `halt`, `destroy`) can be
-used with this ID to control it. For example: `vagrant destroy a1b2c3`.
-
-## Options
-
-* `--prune` - Prunes invalid entries from the list. This is much more time
-  consuming than simply listing the entries.
-
-## Environment Not Showing Up
-
-If your environment is not showing up, you may have to do a `vagrant destroy`
-followed by a `vagrant up`.
-
-If you just upgraded from a previous version of Vagrant, existing environments
-will not show up in global-status until they are destroyed and recreated.

data/vendor/bundle/ruby/2.3.0/bundler/gems/vagrant-04f7215b5e3f/website/source/docs/cli/halt.html.md

@@ -1,29 +0,0 @@
----
-layout: "docs"
-page_title: "vagrant halt - Command-Line Interface"
-sidebar_current: "cli-halt"
-description: |-
-  The "vagrant halt" command is used to shut down the virtual machine that
-  Vagrant is currently managing.
----
-
-# Halt
-
-**Command: `vagrant halt [name|id]`**
-
-This command shuts down the running machine Vagrant is managing.
-
-Vagrant will first attempt to gracefully shut down the machine by running
-the guest OS shutdown mechanism. If this fails, or if the `--force` flag is
-specified, Vagrant will effectively just shut off power to the machine.
-
-For linux-based guests, Vagrant uses the `shutdown` command to gracefully
-terminate the machine. Due to the varying nature of operating systems, the
-`shutdown` command may exist at many different locations in the guest's `$PATH`.
-It is the guest machine's responsibility to properly populate the `$PATH` with
-directory containing the `shutdown` command.
-
-## Options
-
-* `-f` or `--force` - Do not attempt to gracefully shut down the machine.
-  This effectively pulls the power on the guest machine.

data/vendor/bundle/ruby/2.3.0/bundler/gems/vagrant-04f7215b5e3f/website/source/docs/cli/index.html.md

@@ -1,32 +0,0 @@
----
-layout: "docs"
-page_title: "Command-Line Interface"
-sidebar_current: "cli"
-description: |-
-  Almost all interaction with Vagrant is done via the command-line interface.
----
-
-# Command-Line Interface
-
-Almost all interaction with Vagrant is done through the command-line
-interface.
-
-The interface is available using the `vagrant` command, and comes installed
-with Vagrant automatically. The `vagrant` command in turn has many subcommands,
-such as `vagrant up`, `vagrant destroy`, etc.
-
-If you run `vagrant` by itself, help will be displayed showing all available
-subcommands. In addition to this, you can run any Vagrant command with the
-`-h` flag to output help about that specific command. For example, try
-running `vagrant init -h`. The help will output a one sentence synopsis of
-what the command does as well as a list of all the flags the command
-accepts.
-
-In depth documentation and use cases of various Vagrant commands is
-available by reading the appropriate sub-section available in the left
-navigational area of this site.
-
-You may also wish to consult the
-[documentation](/docs/other/environmental-variables.html) regarding the
-environmental variables that can be used to configure and control
-Vagrant in a global way.

data/vendor/bundle/ruby/2.3.0/bundler/gems/vagrant-04f7215b5e3f/website/source/docs/cli/init.html.md

@@ -1,71 +0,0 @@
----
-layout: "docs"
-page_title: "vagrant init - Command-Line Interface"
-sidebar_current: "cli-init"
-description: |-
-  The "vagrant init" command is used to initialize the current directory to be
-  a Vagrant environment by creating an initial Vagrantfile.
----
-
-# Init
-
-**Command: `vagrant init [name [url]]`**
-
-This initializes the current directory to be a Vagrant environment
-by creating an initial [Vagrantfile](/docs/vagrantfile/) if
-one does not already exist.
-
-If a first argument is given, it will prepopulate the `config.vm.box`
-setting in the created Vagrantfile.
-
-If a second argument is given, it will prepopulate the `config.vm.box_url`
-setting in the created Vagrantfile.
-
-## Options
-
-* `--box-version` - (Optional) The box version or box version constraint to add
-  to the `Vagrantfile`.
-
-* `--force` - If specified, this command will overwrite any existing
-  `Vagrantfile`.
-
-* `--minimal` - If specified, a minimal Vagrantfile will be created. This
-  Vagrantfile does not contain the instructional comments that the normal
-  Vagrantfile contains.
-
-* `--output FILE` - This will output the Vagrantfile to the given file.
-  If this is "-", the Vagrantfile will be sent to stdout.
-
-* `--template FILE` - Provide a custom ERB template for generating the Vagrantfile.
-
-## Examples
-
-Create a base Vagrantfile:
-
-```sh
-$ vagrant init hashicorp/precise64
-```
-
-Create a minimal Vagrantfile (no comments or helpers):
-
-```sh
-$ vagrant init -m hashicorp/precise64
-```
-
-Create a new Vagrantfile, overwriting the one at the current path:
-
-```sh
-$ vagrant init -f hashicorp/precise64
-```
-
-Create a Vagrantfile with the specific box, from the specific box URL:
-
-```sh
-$ vagrant init my-company-box https://boxes.company.com/my-company.box
-```
-
-Create a Vagrantfile, locking the box to a version constraint:
-
-```sh
-$ vagrant init --box-version '> 0.1.5' hashicorp/precise64
-```

data/vendor/bundle/ruby/2.3.0/bundler/gems/vagrant-04f7215b5e3f/website/source/docs/cli/login.html.md

@@ -1,64 +0,0 @@
----
-layout: "docs"
-page_title: "vagrant login - Command-Line Interface"
-sidebar_current: "cli-login"
-description: |-
-  The "vagrant login" command is used to authenticate Vagrant with HashiCorp's
-  Vagrant Cloud service to use features like private boxes and "vagrant push".
----
-
-# Login
-
-**Command: `vagrant login`**
-
-The login command is used to authenticate with the
-[HashiCorp's Vagrant Cloud](/docs/vagrant-cloud) server. Logging is only
-necessary if you are accessing protected boxes or using
-[Vagrant Share](/docs/share/).
-
-**Logging in is not a requirement to use Vagrant.** The vast majority
-of Vagrant does _not_ require a login. Only certain features such as protected
-boxes or [Vagrant Share](/docs/share/) require a login.
-
-The reference of available command-line flags to this command
-is available below.
-
-
-## Options
-
-* `--check` - This will check if you are logged in. In addition to outputting
-  whether you are logged in or not, the command will have exit status 0 if you are
-  logged in, and exit status 1 if you are not.
-
-* `--logout` - This will log you out if you are logged in. If you are already
-  logged out, this command will do nothing. It is not an error to call this
-  command if you are already logged out.
-
-* `--token` - This will set the Vagrant Cloud login token manually to the provided
-  string. It is assumed this token is a valid Vagrant Cloud access token.
-
-
-## Examples
-
-Securely authenticate to Vagrant Cloud using a username and password:
-
-```text
-$ vagrant login
-# ...
-Vagrant Cloud username:
-Vagrant Cloud password:
-```
-
-Check if the current user is authenticated:
-
-```text
-$ vagrant login --check
-You are already logged in.
-```
-
-Securely authenticate with Vagrant Cloud using a token:
-
-```text
-$ vagrant login --token ABCD1234
-The token was successfully saved.
-```