vagrant-aws-detiber 0.7.2.pre.2

data/vendor/bundle/ruby/2.3.0/bundler/gems/vagrant-419afb4dcffe/website/source/docs/cli/non-primary.html.md

@@ -0,0 +1,34 @@
+---
+layout: "docs"
+page_title: "More Vagrant Commands - Command-Line Interface"
+sidebar_current: "cli-nonprimary"
+description: |-
+  In addition to the commands listed in the sidebar and shown in "vagrant -h",
+  Vagrant comes with some more commands that are hidden from basic help output.
+  These commands are hidden because they're not useful to beginners or they're
+  not commonly used. We call these commands "non-primary subcommands".
+---
+
+# More Commands
+
+In addition to the commands listed in the sidebar and shown in `vagrant -h`,
+Vagrant comes with some more commands that are hidden from basic help output.
+These commands are hidden because they're not useful to beginners or they're
+not commonly used. We call these commands "non-primary subcommands".
+
+You can view all subcommands, including the non-primary subcommands,
+by running `vagrant list-commands`, which itself is a non-primary subcommand!
+
+Note that while you have to run a special command to list the non-primary
+subcommands, you do not have to do anything special to actually _run_ the
+non-primary subcommands. They're executed just like any other subcommand:
+`vagrant COMMAND`.
+
+The list of non-primary commands is below. Click on any command to learn
+more about it.
+
+* [docker-exec](/docs/docker/commands.html)
+* [docker-logs](/docs/docker/commands.html)
+* [docker-run](/docs/docker/commands.html)
+* [rsync](/docs/cli/rsync.html)
+* [rsync-auto](/docs/cli/rsync-auto.html)

data/vendor/bundle/ruby/2.3.0/bundler/gems/vagrant-419afb4dcffe/website/source/docs/cli/package.html.md

@@ -0,0 +1,44 @@
+---
+layout: "docs"
+page_title: "vagrant package - Command-Line Interface"
+sidebar_current: "cli-package"
+description: |-
+  The "vagrant package" command is used to package a currently-running
+  VirtualBox or Hyper-V vagrant environment into a reusable Vagrant box.
+---
+
+# Package
+
+**Command: `vagrant package [name|id]`**
+
+This packages a currently running _VirtualBox_ or _Hyper-V_ environment into a
+re-usable [box](/docs/boxes.html). This command can only be used with
+other [providers](/docs/providers/) based on the provider implementation
+and if the provider supports it.
+
+## Options
+
+* `--base NAME` - Instead of packaging a VirtualBox machine that Vagrant
+  manages, this will package a VirtualBox machine that VirtualBox manages.
+  `NAME` should be the name or UUID of the machine from the VirtualBox GUI.
+  Currently this option is only available for VirtualBox.
+
+* `--output NAME` - The resulting package will be saved as `NAME`. By default,
+  it will be saved as `package.box`.
+
+* `--include x,y,z` - Additional files will be packaged with the box. These
+  can be used by a packaged Vagrantfile (documented below) to perform additional
+  tasks.
+
+* `--vagrantfile FILE` - Packages a Vagrantfile with the box, that is loaded
+  as part of the [Vagrantfile load order](/docs/vagrantfile/#load-order)
+  when the resulting box is used.
+
+<div class="alert alert-info">
+  <strong>A common misconception</strong> is that the <code>--vagrantfile</code>
+  option will package a Vagrantfile that is used when <code>vagrant init</code>
+  is used with this box. This is not the case. Instead, a Vagrantfile
+  is loaded and read as part of the Vagrant load process when the box is
+  used. For more information, read about the
+  <a href="/docs/vagrantfile/#load-order">Vagrantfile load order</a>.
+</div>

data/vendor/bundle/ruby/2.3.0/bundler/gems/vagrant-419afb4dcffe/website/source/docs/cli/plugin.html.md

@@ -0,0 +1,144 @@
+---
+layout: "docs"
+page_title: "vagrant plugin - Command-Line Interface"
+sidebar_current: "cli-plugin"
+description: |-
+  The "vagrant plugin" command is used to manage Vagrant plugins including
+  installing, uninstalling, and license management.
+---
+
+# Plugin
+
+**Command: `vagrant plugin`**
+
+This is the command used to manage [plugins](/docs/plugins/).
+
+The main functionality of this command is exposed via another level
+of subcommands:
+
+* [`expunge`](#plugin-expunge)
+* [`install`](#plugin-install)
+* [`license`](#plugin-license)
+* [`list`](#plugin-list)
+* [`repair`](#plugin-repair)
+* [`uninstall`](#plugin-uninstall)
+* [`update`](#plugin-update)
+
+# Plugin Expunge
+
+**Command: `vagrant plugin expunge`**
+
+This removes all user installed plugin information. All plugin gems, their
+dependencies, and the `plugins.json` file are removed. This command
+provides a simple mechanism to fully remove all user installed custom plugins.
+
+When upgrading Vagrant it may be required to reinstall plugins due to
+an internal incompatibility. The expunge command can help make that process
+easier by attempting to automatically reinstall currently configured
+plugins:
+
+```shell
+# Delete all plugins and reinstall
+$ vagrant plugin expunge --reinstall
+```
+
+This command accepts optional command-line flags:
+
+* `--force` - Do not prompt for confirmation prior to removal
+* `--reinstall` - Attempt to reinstall plugins after removal
+
+# Plugin Install
+
+**Command: `vagrant plugin install <name>...`**
+
+This installs a plugin with the given name or file path. If the name
+is not a path to a file, then the plugin is installed from remote
+repositories, usually [RubyGems](https://rubygems.org). This command will
+also update a plugin if it is already installed, but you can also use
+`vagrant plugin update` for that.
+
+```shell
+# Installing a plugin from a known gem source
+$ vagrant plugin install my-plugin
+
+# Installing a plugin from a local file source
+$ vagrant plugin install /path/to/my-plugin.gem
+```
+
+If multiple names are specified, multiple plugins will be installed. If
+flags are given below, the flags will apply to _all_ plugins being installed
+by the current command invocation.
+
+If the plugin is already installed, this command will reinstall it with
+the latest version available.
+
+This command accepts optional command-line flags:
+
+* `--entry-point ENTRYPOINT` - By default, installed plugins are loaded
+  internally by loading an initialization file of the same name as the plugin.
+  Most of the time, this is correct. If the plugin you are installing has
+  another entrypoint, this flag can be used to specify it.
+
+* `--plugin-clean-sources` - Clears all sources that have been defined so
+  far. This is an advanced feature. The use case is primarily for corporate
+  firewalls that prevent access to RubyGems.org.
+
+* `--plugin-source SOURCE` - Adds a source from which to fetch a plugin. Note
+  that this does not only affect the single plugin being installed, by all future
+  plugin as well. This is a limitation of the underlying plugin installer
+  Vagrant uses.
+
+* `--plugin-version VERSION` - The version of the plugin to install. By default,
+  this command will install the latest version. You can constrain the version
+  using this flag. You can set it to a specific version, such as "1.2.3" or
+  you can set it to a version constraint, such as "> 1.0.2". You can set it
+  to a more complex constraint by comma-separating multiple constraints:
+  "> 1.0.2, < 1.1.0" (do not forget to quote these on the command-line).
+
+# Plugin License
+
+**Command: `vagrant plugin license <name> <license-file>`**
+
+This command installs a license for a proprietary Vagrant plugin,
+such as the [VMware Fusion provider](/docs/vmware).
+
+# Plugin List
+
+**Command: `vagrant plugin list`**
+
+This lists all installed plugins and their respective installed versions.
+If a version constraint was specified for a plugin when installing it, the
+constraint will be listed as well. Other plugin-specific information may
+be shown, too.
+
+# Plugin Repair
+
+Vagrant may fail to properly initialize user installed custom plugins. This can
+be caused my improper plugin installation/removal, or by manual manipulation of
+plugin related files like the `plugins.json` data file. Vagrant can attempt
+to automatically repair the problem.
+
+If automatic repair is not successful, refer to the [expunge](#plugin-expunge)
+command
+
+# Plugin Uninstall
+
+**Command: `vagrant plugin uninstall <name> [<name2> <name3> ...]`**
+
+This uninstalls the plugin with the given name. Any dependencies of the
+plugin will also be uninstalled assuming no other plugin needs them.
+
+If multiple plugins are given, multiple plugins will be uninstalled.
+
+# Plugin Update
+
+**Command: `vagrant plugin update [<name>]`**
+
+This updates the plugins that are installed within Vagrant. If you specified
+version constraints when installing the plugin, this command will respect
+those constraints. If you want to change a version constraint, re-install
+the plugin using `vagrant plugin install`.
+
+If a name is specified, only that single plugin will be updated. If a
+name is specified of a plugin that is not installed, this command will not
+install it.

data/vendor/bundle/ruby/2.3.0/bundler/gems/vagrant-419afb4dcffe/website/source/docs/cli/port.html.md

@@ -0,0 +1,39 @@
+---
+layout: "docs"
+page_title: "vagrant port - Command-Line Interface"
+sidebar_current: "cli-port"
+description: |-
+  The "vagrant port" command is used to display the full list of guest ports
+  mapped to the host machine ports.
+---
+
+# Port
+
+**Command: `vagrant port [name|id]`**
+
+The port command displays the full list of guest ports mapped to the host
+machine ports:
+
+```
+$ vagrant port
+    22 (guest) => 2222 (host)
+    80 (guest) => 8080 (host)
+```
+
+In a multi-machine Vagrantfile, the name of the machine must be specified:
+
+```
+$ vagrant port my-machine
+```
+
+## Options
+
+* `--guest PORT` - This displays just the host port that corresponds to the
+  given guest port. If the guest is not forwarding that port, an error is
+  returned. This is useful for quick scripting, for example:
+
+        $ ssh -p $(vagrant port --guest 22)
+
+* `--machine-readable` - This tells Vagrant to display machine-readable output
+  instead of the human-friendly output. More information is available in the
+  [machine-readable output](/docs/cli/machine-readable.html) documentation.

data/vendor/bundle/ruby/2.3.0/bundler/gems/vagrant-419afb4dcffe/website/source/docs/cli/powershell.html.md

@@ -0,0 +1,22 @@
+---
+layout: "docs"
+page_title: "vagrant powershell - Command-Line Interface"
+sidebar_current: "cli-powershell"
+description: |-
+  The "vagrant powershell" command is used to open a powershell prompt running
+  inside the guest machine.
+---
+
+# PowerShell
+
+**Command: `vagrant powershell`**
+
+This will open a PowerShell prompt into a running Vagrant machine.
+
+This command will only work if the machine supports PowerShell. Not every
+environment will support PowerShell.
+
+## Options
+
+* `-c COMMAND` or `--command COMMAND` - This executes a single PowerShell command,
+  prints out the stdout and stderr, and exits.

data/vendor/bundle/ruby/2.3.0/bundler/gems/vagrant-419afb4dcffe/website/source/docs/cli/provision.html.md

@@ -0,0 +1,28 @@
+---
+layout: "docs"
+page_title: "vagrant provision - Command-Line Interface"
+sidebar_current: "cli-provision"
+description: |-
+  The "vagrant provision" command is used to run any provisioners configured
+  for the guest machine, such as Puppet, Chef, Ansible, Salt, or Shell.
+---
+
+# Provision
+
+**Command: `vagrant provision [vm-name]`**
+
+Runs any configured [provisioners](/docs/provisioning/)
+against the running Vagrant managed machine.
+
+This command is a great way to quickly test any provisioners, and is especially
+useful for incremental development of shell scripts, Chef cookbooks, or Puppet
+modules. You can just make simple modifications to the provisioning scripts
+on your machine, run a `vagrant provision`, and check for the desired results.
+Rinse and repeat.
+
+# Options
+
+* `--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-419afb4dcffe/website/source/docs/cli/rdp.html.md

@@ -0,0 +1,43 @@
+---
+layout: "docs"
+page_title: "vagrant rdp - Command-Line Interface"
+sidebar_current: "cli-rdp"
+description: |-
+  The "vagrant rdp" command is used to start an RDP client for a remote desktop
+  session with the guest machine.
+---
+
+# RDP
+
+**Command: `vagrant rdp`**
+
+This will start an RDP client for a remote desktop session with the
+guest. This only works for Vagrant environments that support remote
+desktop, which is typically only Windows.
+
+## Raw Arguments
+
+You can pass raw arguments through to your RDP client on the
+command-line by appending it after a `--`. Vagrant just passes
+these through. For example:
+
+```
+$ vagrant rdp -- /span
+```
+
+The above command on Windows will execute `mstsc.exe /span config.rdp`,
+allowing your RDP to span multiple desktops.
+
+
+On Darwin hosts, such as Mac OS X, the additional arguments are added to the
+generated RDP configuration file. Since these files can contain multiple options
+with different spacing, you _must_ quote multiple arguments. For example:
+
+```
+$ vagrant rdp -- "screen mode id:i:0" "other config:s:value"
+```
+
+Note that as of the publishing of this guide, the Microsoft RDP Client for Mac
+does _not_ perform validation on the configuration file. This means if you
+specify an invalid configuration option or make a typographical error, the
+client will silently ignore the error and continue!

data/vendor/bundle/ruby/2.3.0/bundler/gems/vagrant-419afb4dcffe/website/source/docs/cli/reload.html.md

@@ -0,0 +1,31 @@
+---
+layout: "docs"
+page_title: "vagrant reload - Command-Line Interface"
+sidebar_current: "cli-reload"
+description: |-
+  The "vagrant reload" command is the equivalent of running "vagrant halt"
+  followed by "vagrant up".
+---
+
+# Reload
+
+**Command: `vagrant reload [name|id]`**
+
+The equivalent of running a [halt](/docs/cli/halt.html) followed by an
+[up](/docs/cli/up.html).
+
+This command is usually required for changes made in the Vagrantfile to
+take effect. After making any modifications to the Vagrantfile, a `reload`
+should be called.
+
+The configured provisioners will not run again, by default. You can force
+the provisioners to re-run by specifying the `--provision` flag.
+
+# Options
+
+* `--provision` - Force 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 reload --provision-with shell`, only the shell provisioner will
+  be run.

data/vendor/bundle/ruby/2.3.0/bundler/gems/vagrant-419afb4dcffe/website/source/docs/cli/resume.html.md

@@ -0,0 +1,28 @@
+---
+layout: "docs"
+page_title: "vagrant resume - Command-Line Interface"
+sidebar_current: "cli-resume"
+description: |-
+  The "vagrant resume" command is used to bring a machine back into the "up"
+  state, perhaps if it was previously suspended via "vagrant halt" or "vagrant
+  suspend".
+---
+
+# Resume
+
+**Command: `vagrant resume [name|id]`**
+
+This resumes a Vagrant managed machine that was previously suspended,
+perhaps with the [suspend command](/docs/cli/suspend.html).
+
+The configured provisioners will not run again, by default. You can force
+the provisioners to re-run by specifying the `--provision` flag.
+
+# Options
+
+* `--provision` - Force 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-419afb4dcffe/website/source/docs/cli/rsync-auto.html.md

@@ -0,0 +1,52 @@
+---
+layout: "docs"
+page_title: "vagrant rsync-auto - Command-Line Interface"
+sidebar_current: "cli-rsyncauto"
+description: |-
+  The "vagrant rsync-auto" command watches all local directories of any rsync
+  configured synced folders and automatically initiates an rsync transfer when
+  changes are detected.
+---
+
+# rsync-auto
+
+**Command: `vagrant rsync-auto`**
+
+This command watches all local directories of any
+[rsync synced folders](/docs/synced-folders/rsync.html) and automatically
+initiates an rsync transfer when changes are detected. This command does
+not exit until an interrupt is received.
+
+The change detection is optimized to use platform-specific APIs to listen
+for filesystem changes, and does not simply poll the directory.
+
+## Options
+
+* `--[no-]poll` - Force Vagrant to watch for changes using filesystem
+    polling instead of filesystem events. This is required for some filesystems
+    that do not support events. Warning: enabling this will make `rsync-auto`
+    _much_ slower. By default, polling is disabled.
+
+## Machine State Changes
+
+The `rsync-auto` command does not currently handle machine state changes
+gracefully. For example, if you start the `rsync-auto` command, then
+halt the guest machine, then make changes to some files, then boot it
+back up, `rsync-auto` will not attempt to resync.
+
+To ensure that the command works properly, you should start `rsync-auto`
+only when the machine is running, and shut it down before any machine
+state changes.
+
+You can always force a resync with the [rsync](/docs/cli/rsync.html) command.
+
+## Vagrantfile Changes
+
+If you change or move your Vagrantfile, the `rsync-auto` command will have
+to be restarted. For example, if you add synced folders to the Vagrantfile,
+or move the directory that contains the Vagrantfile, the `rsync-auto`
+command will either not pick up the changes or may begin experiencing
+strange behavior.
+
+Before making any such changes, it is recommended that you turn off
+`rsync-auto`, then restart it afterwards.

data/vendor/bundle/ruby/2.3.0/bundler/gems/vagrant-419afb4dcffe/website/source/docs/cli/rsync.html.md

@@ -0,0 +1,18 @@
+---
+layout: "docs"
+page_title: "vagrant rsync - Command-Line Interface"
+sidebar_current: "cli-rsync"
+description: |-
+  The "vagrant rsync" command forces a re-sync of any rsync synced folders.
+---
+
+# Rsync
+
+**Command: `vagrant rsync`**
+
+This command forces a re-sync of any
+[rsync synced folders](/docs/synced-folders/rsync.html).
+
+Note that if you change any settings within the rsync synced folders such
+as exclude paths, you will need to `vagrant reload` before this command will
+pick up those changes.

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

@@ -0,0 +1,49 @@
+---
+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-419afb4dcffe/website/source/docs/cli/snapshot.html.md

@@ -0,0 +1,94 @@
+---
+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.