vagrant-packet 0.1.2 → 0.1.3

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

@@ -1,49 +0,0 @@
----
-layout: "docs"
-page_title: "vagrant share - Command-Line Interface"
-sidebar_current: "cli-share"
-description: |-
-  The "vagrant share" command initializes a new Vagrant share session, which
-  allows you to share your virtual machine with the public Internet.
----
-
-# Share
-
-**Command: `vagrant share`**
-
-The share command initializes a Vagrant Share session, allowing you to
-share your Vagrant environment with anyone in the world, enabling collaboration
-directly in your Vagrant environment in almost any network environment.
-
-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-http` - Disables the creation of a publicly accessible
-  HTTP endpoint to your Vagrant environment. With this set, the only way
-  to access your share is with `vagrant connect`.
-
-* `--http PORT` - The port of the HTTP server running in the Vagrant
-  environment. By default, Vagrant will attempt to find this for you.
-  This has no effect if `--disable-http` is set.
-
-* `--https PORT` - The port of an HTTPS server running in the Vagrant
-  environment. By default, Vagrant will attempt to find this for you.
-  This has no effect if `--disable-http` is set.
-
-* `--ssh` - Enables SSH sharing (more information below). By default, this
-  is not enabled.
-
-* `--ssh-no-password` - Disables the encryption of the SSH keypair created
-  when SSH sharing is enabled.
-
-* `--ssh-port PORT` - The port of the SSH server running in the Vagrant
-  environment. By default, Vagrant will attempt to find this for you.
-
-* `--ssh-once` - Allows SSH access only once. After the first attempt to
-  connect via SSH to the Vagrant environment, the generated keypair is
-  destroyed.

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

@@ -1,94 +0,0 @@
----
-layout: "docs"
-page_title: "vagrant snapshot - Command-Line Interface"
-sidebar_current: "cli-snapshot"
-description: |-
-  The "vagrant snapshot" command is used to manage snapshots of the guest
-  machine.
----
-
-# Snapshot
-
-**Command: `vagrant snapshot`**
-
-This is the command used to manage snapshots with the guest machine.
-Snapshots record a point-in-time state of a guest machine. You can then
-quickly restore to this environment. This lets you experiment and try things
-and quickly restore back to a previous state.
-
-Snapshotting is not supported by every provider. If it is not supported,
-Vagrant will give you an error message.
-
-The main functionality of this command is exposed via even more subcommands:
-
-* [`push`](#snapshot-push)
-* [`pop`](#snapshot-pop)
-* [`save`](#snapshot-save)
-* [`restore`](#snapshot-restore)
-* [`list`](#snapshot-list)
-* [`delete`](#snapshot-delete)
-
-# Snapshot Push
-
-**Command: `vagrant snapshot push`**
-
-This takes a snapshot and pushes it onto the snapshot stack.
-
-This is a shorthand for `vagrant snapshot save` where you do not need
-to specify a name. When you call the inverse `vagrant snapshot pop`, it will
-restore the pushed state.
-
-~> **Warning:** If you are using `push` and `pop`, avoid using `save`
-   and `restore` which are unsafe to mix.
-
-# Snapshot Pop
-
-**Command: `vagrant snapshot pop`**
-
-This command is the inverse of `vagrant snapshot push`: it will restore
-the pushed state.
-
-## Options
-
-* `--[no-]provision` - Force the provisioners to run (or prevent them
-    from doing so).
-
-* `--no-delete` - Prevents deletion of the snapshot after restoring
-    (so that you can restore to the same point again later).
-
-# Snapshot Save
-
-**Command: `vagrant snapshot save [vm-name] NAME`**
-
-This command saves a new named snapshot. If this command is used, the
-`push` and `pop` subcommands cannot be safely used.
-
-# Snapshot Restore
-
-**Command: `vagrant snapshot restore [vm-name] NAME`**
-
-This command restores the named snapshot.
-
-* `--[no-]provision` - Force the provisioners to run (or prevent them
-    from doing so).
-
-# Snapshot List
-
-**Command: `vagrant snapshot list`**
-
-This command will list all the snapshots taken.
-
-# Snapshot Delete
-
-**Command: `vagrant snapshot delete NAME`**
-
-This command will delete the named snapshot.
-
-Some providers require all "child" snapshots to be deleted first. Vagrant
-itself does not track what these children are. If this is the case (such
-as with VirtualBox), then you must be sure to delete the snapshots in the
-reverse order they were taken.
-
-This command is typically _much faster_ if the machine is halted prior to
-snapshotting. If this is not an option, or is not ideal, then the deletion
-can also be done online with most providers.

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

@@ -1,51 +0,0 @@
----
-layout: "docs"
-page_title: "vagrant ssh - Command-Line Interface"
-sidebar_current: "cli-ssh"
-description: |-
-  The "vagrant ssh" command is used to establish an SSH session into a running
-  virtual machine to give you shell access.
----
-
-# SSH
-
-**Command: `vagrant ssh [name|id] [-- extra_ssh_args]`**
-
-This will SSH into a running Vagrant machine and give you access to a shell.
-
-If a `--` (two hyphens) are found on the command line, any arguments after
-this are passed directly into the `ssh` executable. This allows you to pass
-any arbitrary commands to do things such as reverse tunneling down into the
-`ssh` program.
-
-## Options
-
-* `-c COMMAND` or `--command COMMAND` - This executes a single SSH command, prints
-  out the stdout and stderr, and exits.
-
-* `-p` or `--plain` - This does an SSH without authentication, leaving
-  authentication up to the user.
-
-## SSH client usage
-
-Vagrant will attempt to use the local SSH client installed on the host machine. On
-POSIX machines, an SSH client must be installed and available on the PATH.
-
-For Windows installations, an SSH client is provided within the installer
-image. If no SSH client is found on the current PATH, Vagrant will use the
-SSH client it provided. Depending on the local environment used for running
-Vagrant, the installer provided SSH client may not work correctly. For example,
-when using a cygwin or msys2 shell the SSH client will fail to work as expected
-when run interactively. Installing the SSH package built for the current working
-environment will resolve this issue.
-
-## Background Execution
-
-If the command you specify runs in the background (such as appending a `&` to
-a shell command), it will be terminated almost immediately. This is because
-when Vagrant executes the command, it executes it within the context of a
-shell, and when the shell exits, all of the child processes also exit.
-
-To avoid this, you will need to detach the process from the shell. Please
-Google to learn how to do this for your shell. One method of doing this is
-the `nohup` command.

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

@@ -1,20 +0,0 @@
----
-layout: "docs"
-page_title: "vagrant ssh-config - Command-Line Interface"
-sidebar_current: "cli-ssh_config"
-description: |-
-  The "vagrant ssh-config" command is used to output a valid SSH configuration
-  file capable of SSHing into the guest machine directly.
----
-
-# SSH Config
-
-**Command: `vagrant ssh-config [name|id]`**
-
-This will output valid configuration for an SSH config file to SSH
-into the running Vagrant machine from `ssh` directly (instead of
-using `vagrant ssh`).
-
-## Options
-
-* `--host NAME` - Name of the host for the outputted configuration.

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

@@ -1,18 +0,0 @@
----
-layout: "docs"
-page_title: "vagrant status - Command-Line Interface"
-sidebar_current: "cli-status"
-description: |-
-  The "vagrant status" command is used to tell you the status of the virtual
-  machines in the current Vagrant environment.
----
-
-# Status
-
-**Command: `vagrant status [name|id]`**
-
-This will tell you the state of the machines Vagrant is managing.
-
-It is quite easy, especially once you get comfortable with Vagrant, to
-forget whether your Vagrant machine is running, suspended, not created, etc.
-This command tells you the state of the underlying guest machine.

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

@@ -1,23 +0,0 @@
----
-layout: "docs"
-page_title: "vagrant suspend - Command-Line Interface"
-sidebar_current: "cli-suspend"
-description: |-
-  The "vagrant suspend" command is used to suspend the guest machine Vagrant is
-  currently managing.
----
-
-# Suspend
-
-**Command: `vagrant suspend [name|id]`**
-
-This suspends the guest machine Vagrant is managing, rather than fully
-[shutting it down](/docs/cli/halt.html) or [destroying it](/docs/cli/destroy.html).
-
-A suspend effectively saves the _exact point-in-time state_ of the machine,
-so that when you [resume](/docs/cli/resume.html) it later, it begins running
-immediately from that point, rather than doing a full boot.
-
-This generally requires extra disk space to store all the contents of the
-RAM within your guest machine, but the machine no longer consumes the
-RAM of your host machine or CPU cycles while it is suspended.

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

@@ -1,48 +0,0 @@
----
-layout: "docs"
-page_title: "vagrant up - Command-Line Interface"
-sidebar_current: "cli-up"
-description: |-
-  The "vagrant up" command is used to create, configuration, and provision a
-  guest machine according to your Vagrantfile.
----
-
-# Up
-
-**Command: `vagrant up [name|id]`**
-
-This command creates and configures guest machines according to your
-[Vagrantfile](/docs/vagrantfile/).
-
-This is the single most important command in Vagrant, since it is how
-any Vagrant machine is created. Anyone using Vagrant must use this command
-on a day-to-day basis.
-
-## Options
-
-* `name` - Name of machine defined in [Vagrantfile](/docs/vagrantfile/)
-
-* `id` - Machine id found with `vagrant global-status`. Using `id` allows
-  you to call `vagrant up id` from any directory.
-
-* `--[no-]destroy-on-error` - Destroy the newly created machine if a fatal,
-  unexpected error occurs. This will only happen on the first `vagrant up`.
-  By default this is set.
-
-* `--[no-]install-provider` - If the requested provider is not installed,
-  Vagrant will attempt to automatically install it if it can. By default this
-  is enabled.
-
-* `--[no-]parallel` - Bring multiple machines up in parallel if the provider
-  supports it. Please consult the provider documentation to see if this feature
-  is supported.
-
-* `--provider x` - Bring the machine up with the given
-  [provider](/docs/providers/). By default this is "virtualbox".
-
-* `--[no-]provision` - Force, or prevent, the provisioners to run.
-
-* `--provision-with x,y,z` - This will only run the given provisioners. For
-  example, if you have a `:shell` and `:chef_solo` provisioner and run
-  `vagrant provision --provision-with shell`, only the shell provisioner will
-  be run.

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

@@ -1,20 +0,0 @@
----
-layout: "docs"
-page_title: "vagrant validate - Command-Line Interface"
-sidebar_current: "cli-validate"
-description: |-
-  The "vagrant validate" command is used to validate your Vagrantfile.
----
-
-# Validate
-
-**Command: `vagrant validate`**
-
-This command validates your [Vagrantfile](/docs/vagrantfile/).
-
-## Examples
-
-```sh
-$ vagrant validate
-Vagrantfile validated successfully.
-```

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

@@ -1,19 +0,0 @@
----
-layout: "docs"
-page_title: "vagrant version - Command-Line Interface"
-sidebar_current: "cli-version"
-description: |-
-  The "vagrant version" command is used to output the version of Vagrant
-  currently installed on the system.
----
-
-# Version
-
-**Command: `vagrant version`**
-
-This command tells you the version of Vagrant you have installed
-as well as the latest version of Vagrant that is currently available.
-
-In order to determine the latest available Vagrant version, this
-command must make a network call. If you only want to see the currently
-installed version, use `vagrant --version`.

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

@@ -1,120 +0,0 @@
----
-layout: "docs"
-page_title: "Basic Usage - Docker Provider"
-sidebar_current: "providers-docker-basics"
-description: |-
-  The Docker provider in Vagrant behaves just like any other provider.
-  If you are familiar with Vagrant already, then using the Docker provider
-  should be intuitive and simple.
----
-
-# Docker Basic Usage
-
-The Docker provider in Vagrant behaves just like any other provider.
-If you are familiar with Vagrant already, then using the Docker provider
-should be intuitive and simple.
-
-The Docker provider _does not_ require a `config.vm.box` setting. Since
-the "base image" for a Docker container is pulled from the
-Docker Index or
-built from a Dockerfile, the box does not
-add much value, and is optional for this provider.
-
-## Docker Images
-
-The first method that Vagrant can use to source a Docker container
-is via an image. This image can be from any Docker registry. An
-example is shown below:
-
-```ruby
-Vagrant.configure("2") do |config|
-  config.vm.provider "docker" do |d|
-    d.image = "foo/bar"
-  end
-end
-```
-
-When `vagrant up --provider=docker` is run, this will bring up the
-image `foo/bar`.
-
-This is useful for extra components of your application that it might
-depend on: databases, queues, etc. Typically, the primary application
-you are working on is built with a Dockerfile, or via a container with
-SSH.
-
-## Dockerfiles
-
-Vagrant can also automatically build and run images based on a local
-Dockerfile. This is useful for iterating on an application locally
-that is built into an image later. An example is shown below:
-
-```ruby
-Vagrant.configure("2") do |config|
-  config.vm.provider "docker" do |d|
-    d.build_dir = "."
-  end
-end
-```
-
-The above configuration will look for a `Dockerfile` in the same
-directory as the Vagrantfile. When `vagrant up --provider=docker` is run, Vagrant
-automatically builds that Dockerfile and starts a container
-based on that Dockerfile.
-
-The Dockerfile is rebuilt when `vagrant reload` is called.
-
-## Synced Folders and Networking
-
-When using Docker, Vagrant automatically converts synced folders
-and networking options into Docker volumes and forwarded ports.
-You do not have to use the Docker-specific configurations to do this.
-This helps keep your Vagrantfile similar to how it has always looked.
-
-The Docker provider does not support specifying options for `owner` or `group`
-on folders synced with a docker container.
-
-Private and public networks are not currently supported.
-
-## Host VM
-
-If the system cannot run Linux containers natively, Vagrant automatically spins
-up a "host VM" to run Docker. This allows your Docker-based Vagrant environments
-to remain portable, without inconsistencies depending on the platform they are
-running on.
-
-Vagrant will spin up a single instance of a host VM and run multiple
-containers on this one VM. This means that with the Docker provider,
-you only have the overhead of one virtual machine, and only if it is
-absolutely necessary.
-
-By default, the host VM Vagrant spins up is
-[backed by boot2docker](https://github.com/hashicorp/vagrant/blob/master/plugins/providers/docker/hostmachine/Vagrantfile),
-because it launches quickly and uses little resources. But the host VM
-can be customized to point to _any_ Vagrantfile. This allows the host VM
-to more closely match production by running a VM running Ubuntu, RHEL,
-etc. It can run any operating system supported by Vagrant.
-
-<div class="alert alert-info">
-  <strong>Synced folder note:</strong> Vagrant will attempt to use the
-  "best" synced folder implementation it can. For boot2docker, this is
-  often rsync. In this case, make sure you have rsync installed on your
-  host machine. Vagrant will give you a human-friendly error message if
-  it is not.
-</div>
-
-An example of changing the host VM is shown below. Remember that this
-is optional, and Vagrant will spin up a default host VM if it is not
-specified:
-
-```ruby
-Vagrant.configure("2") do |config|
-  config.vm.provider "docker" do |d|
-    d.vagrant_vagrantfile = "../path/to/Vagrantfile"
-  end
-end
-```
-
-The host VM will be spun up at the first `vagrant up` where the provider
-is Docker. To control this host VM, use the
-[global-status command](/docs/cli/global-status.html)
-along with global control.

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

@@ -1,20 +0,0 @@
----
-layout: "docs"
-page_title: "Boxes - Docker Provider"
-sidebar_current: "providers-docker-boxes"
-description: |-
-  The Docker provider does not require a Vagrant box. The "config.vm.box"
-  setting is completely optional.
----
-
-# Docker Boxes
-
-The Docker provider does not require a Vagrant box. The `config.vm.box`
-setting is completely optional.
-
-A box can still be used and specified, however, to provide defaults.
-Because the `Vagrantfile` within a box is loaded as part of the
-configuration loading sequence, it can be used to configure the
-foundation of a development environment.
-
-In general, however, you will not need a box with the Docker provider.

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

@@ -1,113 +0,0 @@
----
-layout: "docs"
-page_title: "Commands - Docker Provider"
-sidebar_current: "providers-docker-commands"
-description: |-
-  The Docker provider exposes some additional Vagrant commands that are
-  useful for interacting with Docker containers. This helps with your
-  workflow on top of Vagrant so that you have full access to Docker
-  underneath.
----
-
-# Docker Commands
-
-The Docker provider exposes some additional Vagrant commands that are
-useful for interacting with Docker containers. This helps with your
-workflow on top of Vagrant so that you have full access to Docker
-underneath.
-
-### docker-exec
-
-`vagrant docker-exec` can be used to run one-off commands against
-a Docker container that is currently running. If the container is not running,
-an error will be returned.
-
-```sh
-$ vagrant docker-exec app -- rake db:migrate
-```
-
-The above would run `rake db:migrate` in the context of an `app` container.
-
-Note that the "name" corresponds to the name of the VM, **not** the name of the
-Docker container. Consider the following Vagrantfile:
-
-```ruby
-Vagrant.configure(2) do |config|
-  config.vm.provider "docker" do |d|
-    d.image = "consul"
-  end
-end
-```
-
-This Vagrantfile will start the official Docker Consul image. However, the
-associated Vagrant command to `docker-exec` into this instance is:
-
-```sh
-$ vagrant docker-exec -it -- /bin/sh
-```
-
-In particular, the command is actually:
-
-```sh
-$ vagrant docker-exec default -it -- /bin/sh
-```
-
-Because "default" is the default name of the first defined VM. In a
-multi-machine Vagrant setup as shown below, the "name" attribute corresponds
-to the name of the VM, **not** the name of the container:
-
-```ruby
-Vagrant.configure do |config|
-  config.vm.define "web" do
-    config.vm.provider "docker" do |d|
-      d.image = "nginx"
-    end
-  end
-
-  config.vm.define "consul" do
-    config.vm.provider "docker" do |d|
-      d.image = "consul"
-    end
-  end
-end
-```
-
-The following command is invalid:
-
-```sh
-# Not valid
-$ vagrant docker-exec -it nginx -- /bin/sh
-```
-
-This is because the "name" of the VM is "web", so the command is actually:
-
-```sh
-$ vagrant docker-exec -it web -- /bin/sh
-```
-
-For this reason, it is recommended that you name the VM the same as the
-container. In the above example, it is unambiguous that the command to enter
-the Consul container is:
-
-```sh
-$ vagrant docker-exec -it consul -- /bin/sh
-```
-
-### docker-logs
-
-`vagrant docker-logs` can be used to see the logs of a running container.
-Because most Docker containers are single-process, this is used to see
-the logs of that one process. Additionally, the logs can be tailed.
-
-### docker-run
-
-`vagrant docker-run` can be used to run one-off commands against
-a Docker container. The one-off Docker container that is started shares
-all the volumes, links, etc. of the original Docker container. An
-example is shown below:
-
-```sh
-$ vagrant docker-run app -- rake db:migrate
-```
-
-The above would run `rake db:migrate` in the context of an `app` container.