vagrant-packet 0.1.2 → 0.1.3

data/vendor/bundle/ruby/2.4.0/bundler/gems/vagrant-04f7215b5e3f/website/source/docs/push/heroku.html.md

@@ -1,62 +0,0 @@
----
-layout: "docs"
-page_title: "Vagrant Push - Heroku Strategy"
-sidebar_current: "push-heroku"
-description: |-
-  The Vagrant Push Heroku strategy pushes your application's code to Heroku.
-  Only files which are committed to the Git repository are pushed to Heroku.
----
-
-# Vagrant Push
-
-## Heroku Strategy
-
-[Heroku][] is a public PAAS provider that makes it easy to deploy an
-application. The Vagrant Push Heroku strategy pushes your application's code to
-Heroku.
-
-<div class="alert alert-warning">
-  <strong>Warning:</strong> The Vagrant Push Heroku strategy requires you
-  have configured your Heroku credentials and created the Heroku application.
-  This documentation will not cover these prerequisites, but you can read more
-  about them in the <a href="https://devcenter.heroku.com">Heroku documentation</a>.
-</div>
-
-Only files which are committed to the Git repository will be pushed to Heroku.
-Additionally, the current working branch is always pushed to the Heroku, even if
-it is not the "master" branch.
-
-The Vagrant Push Heroku strategy supports the following configuration options:
-
-- `app` - The name of the Heroku application. If the Heroku application does not
-  exist, an exception will be raised. If this value is not specified, the
-  basename of the directory containing the `Vagrantfile` is assumed to be the
-  name of the Heroku application. Since this value can change between users, it
-  is highly recommended that you add the `app` setting to your `Vagrantfile`.
-
-- `dir` - The base directory containing the Git repository to upload to Heroku.
-  By default this is the same directory as the Vagrantfile, but you can specify
-  this if you have a nested Git directory.
-
-- `remote` - The name of the Git remote where Heroku is configured. The default
-  value is "heroku".
-
-
-### Usage
-
-The Vagrant Push Heroku strategy is defined in the `Vagrantfile` using the
-`heroku` key:
-
-```ruby
-config.push.define "heroku" do |push|
-  push.app = "my_application"
-end
-```
-
-And then push the application to Heroku:
-
-```shell
-$ vagrant push
-```
-
-[Heroku]: https://heroku.com/  "Heroku"

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

@@ -1,59 +0,0 @@
----
-layout: "docs"
-page_title: "Vagrant Push"
-sidebar_current: "push"
-description: |-
-  Vagrant Push is a revolutionary feature that allows users to push the code in
-  their Vagrant environment to a remote location.
----
-
-# Vagrant Push
-
-As of version 1.7, Vagrant is capable of deploying or "pushing" application code
-in the same directory as your Vagrantfile to a remote such as an FTP server.
-
-Pushes are defined in an application's `Vagrantfile` and are invoked using the
-`vagrant push` subcommand. Much like other components of Vagrant, each Vagrant
-Push plugin has its own configuration options. Please consult the documentation
-for your Vagrant Push plugin for more information. Here is an example Vagrant
-Push configuration section in a `Vagrantfile`:
-
-```ruby
-config.push.define "ftp" do |push|
-  push.host = "ftp.company.com"
-  push.username = "..."
-  # ...
-end
-```
-
-When the application is ready to be deployed to the FTP server, just run a
-single command:
-
-```shell
-$ vagrant push
-```
-
-Much like [Vagrant Providers][], Vagrant Push also supports multiple backend
-declarations. Consider the common scenario of a staging and QA environment:
-
-```ruby
-config.push.define "staging", strategy: "ftp" do |push|
-  # ...
-end
-
-config.push.define "qa", strategy: "ftp" do |push|
-  # ...
-end
-```
-
-In this scenario, the user must pass the name of the Vagrant Push to the
-subcommand:
-
-```shell
-$ vagrant push staging
-```
-
-Vagrant Push is the easiest way to deploy your application. You can read more
-in the documentation links on the sidebar.
-
-[Vagrant Providers]: /docs/providers/  "Vagrant Providers"

data/vendor/bundle/ruby/2.4.0/bundler/gems/vagrant-04f7215b5e3f/website/source/docs/push/local-exec.html.md

@@ -1,80 +0,0 @@
----
-layout: "docs"
-page_title: "Vagrant Push - Local Exec Strategy"
-sidebar_current: "push-local-exec"
-description: |-
-  The Vagrant Push Local Exec strategy pushes your application's code using a
-  user-defined script.
----
-
-# Vagrant Push
-
-## Local Exec Strategy
-
-The Vagrant Push Local Exec strategy allows the user to invoke an arbitrary
-shell command or script as part of a push.
-
-<div class="alert alert-warning">
-  <strong>Warning:</strong> The Vagrant Push Local Exec strategy does not
-  perform any validation on the correctness of the shell script.
-</div>
-
-The Vagrant Push Local Exec strategy supports the following configuration
-options:
-
-- `script` - The path to a script on disk (relative to the `Vagrantfile`) to
-  execute. Vagrant will attempt to convert this script to an executable, but an
-  exception will be raised if that fails.
-- `inline` - The inline script to execute (as a string).
-- `args` (string or array) - Optional arguments to pass to the shell script when executing it
-  as a single string. These arguments must be written as if they were typed
-  directly on the command line, so be sure to escape characters, quote,
-  etc. as needed. You may also pass the arguments in using an array. In this
-  case, Vagrant will handle quoting for you.
-
-Please note - only one of the `script` and `inline` options may be specified in
-a single push definition.
-
-### Usage
-
-The Vagrant Push Local Exec strategy is defined in the `Vagrantfile` using the
-`local-exec` key:
-
-Remote path:
-
-```ruby
-config.push.define "local-exec" do |push|
-  push.inline = <<-SCRIPT
-    scp -r . server:/var/www/website
-  SCRIPT
-end
-```
-
-Local path:
-
-```ruby
-config.push.define "local-exec" do |push|
-  push.inline = <<-SCRIPT
-    cp -r . /var/www/website
-  SCRIPT
-end
-```
-
-For more complicated scripts, you may store them in a separate file and read
-them from the `Vagrantfile` like so:
-
-```ruby
-config.push.define "local-exec" do |push|
-  push.script = "my-script.sh"
-end
-```
-
-And then invoke the push with Vagrant:
-
-```shell
-$ vagrant push
-```
-
-### Script Arguments
-
-Refer to [Shell Provisioner](/docs/provisioning/shell.html).

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

@@ -1,54 +0,0 @@
----
-layout: "docs"
-page_title: "Vagrant Connect - Vagrant Share"
-sidebar_current: "share-connect"
-description: |-
-  Vagrant can share any or every port to your Vagrant environment, not
-  just SSH and HTTP.
----
-
-# Vagrant Connect
-
-Vagrant can share any or _every_ port to your Vagrant environment, not
-just SSH and HTTP. The `vagrant connect` command gives the connecting person
-a static IP they can use to communicate to the shared Vagrant environment.
-Any TCP traffic sent to this IP is sent to the shared Vagrant environment.
-
-## Usage
-
-Just call `vagrant share --full`. This will automatically share as many ports as
-possible for remote connections. Please see
-[the Vagrant share security page](/docs/share/security.html) for more
-information.
-
-Note the share name at the end of calling `vagrant share --full`, and give this to
-the person who wants to connect to your machine. They simply have to call
-`vagrant connect NAME`. This will give them a static IP they can use to access
-your Vagrant environment.
-
-## How does it work?
-
-`vagrant connect` works by doing what Vagrant does best: managing virtual
-machines. `vagrant connect` creates a tiny virtual machine that takes up
-only around 20 MB in RAM, using VirtualBox or VMware (more provider support
-is coming soon).
-
-Any traffic sent to this tiny virtual machine is then proxied through to
-the shared Vagrant environment as if it were directed at it.
-
-## Beware: Vagrant Insecure Key
-
-If the Vagrant environment or box you are using is protected with the
-Vagrant insecure keypair (most public boxes are), then SSH will be easily
-available to anyone who connects.
-
-While hopefully you are sharing with someone you trust, in certain environments
-you might be sharing with a class, or a conference, and you do not want them
-to be able to SSH in.
-
-In this case, we recommend changing or removing the insecure key from
-the Vagrant machine.
-
-Finally, we want to note that we are working on making it so that when
-Vagrant share is used, the Vagrant private key is actively rejected unless
-explicitly allowed. This feature is not yet done, however.

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

@@ -1,88 +0,0 @@
----
-layout: "docs"
-page_title: "HTTP Sharing - Vagrant Share"
-sidebar_current: "share-http"
-description: |-
-  Vagrant Share can create a publicly accessible URL endpoint to access an
-  HTTP server running in your Vagrant environment. This is known as "HTTP
-  sharing," and is enabled by default when "vagrant share" is used.
----
-
-# HTTP Sharing
-
-Vagrant Share can create a publicly accessible URL endpoint to access an
-HTTP server running in your Vagrant environment. This is known as "HTTP
-sharing," and is enabled by default when `vagrant share` is used.
-
-Because this mode of sharing creates a publicly accessible URL, the accessing
-party does not need to have Vagrant installed in order to view your environment.
-
-This has a number of useful use cases: you can test webhooks by exposing
-your Vagrant environment to the internet, you can show your work to clients,
-teammates, or managers, etc.
-
-## Usage
-
-To use HTTP sharing, simply run `vagrant share`:
-
-```
-$ vagrant share
-==> default: Detecting network information for machine...
-default: Local machine address: 192.168.84.130
-default: Local HTTP port: 9999
-default: Local HTTPS port: disabled
-==> default: Creating Vagrant Share session...
-==> default: HTTP URL: http://b1fb1f3f.ngrok.io
-```
-
-Vagrant detects where your HTTP server is running in your Vagrant environment
-and outputs the endpoint that can be used to access this share. Just give
-this URL to anyone you want to share it with, and they will be able to access
-your Vagrant environment!
-
-If Vagrant has trouble detecting the port of your servers in your environment,
-use the `--http` and/or `--https` flags to be more explicit.
-
-The share will be accessible for the duration that `vagrant share` is running.
-Press `Ctrl-C` to quit the sharing session.
-
-<div class="alert alert-warning">
-  <strong>Warning:</strong> This URL is accessible by <em>anyone</em>
-  who knows it, so be careful if you are sharing sensitive information.
-</div>
-
-## Disabling
-
-If you want to disable the creation of the publicly accessible endpoint,
-run `vagrant share` with the `--disable-http` flag. This will share your
-environment using one of the other methods available, and will not create
-the URL endpoint.
-
-## Missing Assets
-
-Shared web applications must use **relative paths** for loading any
-local assets such as images, stylesheets, javascript.
-
-The web application under development will be accessed remotely. This means
-that if you have any hardcoded asset (images, stylesheets, etc.) URLs
-such as `<img src="http://127.0.0.1/header.png">`, then they will not load
-for people accessing your share.
-
-Most web frameworks or toolkits have settings or helpers to generate
-relative paths. For example, if you are a WordPress developer, the
-[Root Relative URLs](http://wordpress.org/plugins/root-relative-urls/) plugin
-will automatically do this for you.
-
-Relative URLs to assets is generally a best practice in general, so you
-should do this anyways!
-
-## HTTPS (SSL)
-
-Vagrant Share can also expose an SSL port that can be accessed over
-SSL. Creating an HTTPS share requires a non-free ngrok account.
-
-`vagrant share` by default looks for any SSL traffic on port 443 in your
-development environment. If it cannot find any, then SSL is disabled by
-default.
-
-The HTTPS share can be explicitly disabled using the `--disable-https` flag.

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

@@ -1,51 +0,0 @@
----
-layout: "docs"
-page_title: "Vagrant Share"
-sidebar_current: "share"
-description: |-
-  Vagrant Share allows you to  share your Vagrant environment with anyone in
-  the world, enabling collaboration directly in your Vagrant environment
-  in almost any network environment with just a single command- "vagrant share".
----
-
-# Vagrant Share
-
-Vagrant Share allows you to  share your Vagrant environment with anyone in
-the world, enabling collaboration directly in your Vagrant environment
-in almost any network environment with just a single command:
-`vagrant share`.
-
-Vagrant share has three primary modes or features. These features are not
-mutually exclusive, meaning that any combination of them can be active
-at any given time:
-
-  * **HTTP sharing** will create a URL that you can give to anyone. This
-    URL will route directly into your Vagrant environment. The person using
-    this URL does not need Vagrant installed, so it can be shared with anyone.
-    This is useful for testing webhooks or showing your work to clients,
-    teammates, managers, etc.
-
-  * **SSH sharing** will allow instant SSH access to your Vagrant environment
-    by anyone by running `vagrant connect --ssh` on the remote side. This
-    is useful for pair programming, debugging ops problems, etc.
-
-  * **General sharing** allows anyone to access any exposed port of your
-    Vagrant environment by running `vagrant connect` on the remote side.
-    This is useful if the remote side wants to access your Vagrant
-    environment as if it were a computer on the LAN.
-
-The details of each are covered in their specific section in the sidebar
-to the left. We also have a section where we go into detail about the
-security implications of this feature.
-
-## Installation
-
-Vagrant Share is a Vagrant plugin that must be installed. It is not
-included with Vagrant system packages. To install the Vagrant Share
-plugin, run the following command:
-
-```shell
-$ vagrant plugin install vagrant-share
-```
-
-Vagrant Share requires [ngrok](https://ngrok.com) to be used.

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

@@ -1,28 +0,0 @@
----
-layout: "docs"
-page_title: "Custom Provider - Vagrant Share"
-sidebar_current: "share-provider"
-description: |-
-  If you are developing a custom Vagrant provider, you will need to do a tiny
-  bit more work in order for it to work well with Vagrant Share.
----
-
-# Custom Provider
-
-<div class="alert alert-warning">
-  <strong>Warning: Advanced Topic!</strong> This topic is related to
-  developing Vagrant plugins. If you are not interested in this or
-  you are just starting with Vagrant, it is safe to skip this page.
-</div>
-
-If you are developing a [custom Vagrant provider](/docs/plugins/providers.html),
-you will need to do a tiny bit more work in order for it to work well with
-Vagrant Share.
-
-For now, this is only one step:
-
-  * `public_address` provider capability - You must implement this capability
-  to return a string that is an address that can be used to access the
-  guest from Vagrant. This does not need to be a globally routable address,
-  it only needs to be accessible from the machine running Vagrant. If you
-  cannot detect an address, return `nil`.

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

@@ -1,37 +0,0 @@
----
-layout: "docs"
-page_title: "Security - Vagrant Share"
-sidebar_current: "share-security"
-description: |-
-  Sharing your Vagrant environment understandably raises a number of security
-  concerns.
----
-
-# Security
-
-Sharing your Vagrant environment understandably raises a number of security
-concerns.
-
-The primary security mechanism for Vagrant
-Share is security through obscurity along with an encryption key for SSH.
-Additionally, there are several configuration options made available to
-help control access and manage security:
-
-  * `--disable-http` will not create a publicly accessible HTTP URL. When
-    this is set, the only way to access the share is with `vagrant connect`.
-
-In addition to these options, there are other features we've built to help:
-
-  * Vagrant share uses end-to-end TLS for non-HTTP connections. So even unencrypted
-    TCP streams are encrypted through the various proxies and only unencrypted during
-    the final local communication between the local proxy and the Vagrant environment.
-
-  * SSH keys are encrypted by default, using a password that is not transmitted
-    to our servers or across the network at all.
-
-  * SSH is not shared by default, it must explicitly be shared with the
-    `--ssh` flag.
-
-Most importantly, you must understand that by running `vagrant share`,
-you are making your Vagrant environment accessible by anyone who knows
-the share name. When share is not running, it is not accessible.

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

@@ -1,101 +0,0 @@
----
-layout: "docs"
-page_title: "SSH Sharing - Vagrant Share"
-sidebar_current: "share-ssh"
-description: |-
-  Vagrant share makes it trivially easy to allow remote SSH access to your
-  Vagrant environment by supplying the "--ssh" flag to "vagrant share".
----
-
-# SSH Sharing
-
-Vagrant share makes it trivially easy to allow remote SSH access to your
-Vagrant environment by supplying the `--ssh` flag to `vagrant share`.
-
-Easy SSH sharing is incredibly useful if you want to give access to
-a colleague for troubleshooting ops issues. Additionally, it enables
-pair programming with a Vagrant environment, if you want!
-
-SSH sharing is disabled by default as a security measure. To enable
-SSH sharing, simply supply the `--ssh` flag when calling `vagrant share`.
-
-## Usage
-
-Just run `vagrant share --ssh`!
-
-When SSH sharing is enabled, Vagrant generates a brand new keypair for
-SSH access. The public key portion is automatically inserted
-into the Vagrant machine, and the private key portion is provided to the
-user connecting to the Vagrant share. This private key is encrypted using
-a password that you will be prompted for. This password is _never_ transmitted
-across the network by Vagrant, and is an extra layer of security preventing
-anyone who may know your share name from easily accessing your machine.
-
-After running `vagrant share --ssh`, it will output the name of your share:
-
-```
-$ vagrant share --ssh
-==> default: Detecting network information for machine...
-default: Local machine address: 192.168.84.130
-==> default: Generating new SSH key...
-default: Please enter a password to encrypt the key:
-default: Repeat the password to confirm:
-default: Inserting generated SSH key into machine...
-default: Local HTTP port: disabled
-default: Local HTTPS port: disabled
-default: SSH Port: 2200
-==> default: Creating Vagrant Share session...
-share: Cloning VMware VM: 'hashicorp/vagrant-share'. This can take some time...
-share: Verifying vmnet devices are healthy...
-share: Preparing network adapters...
-share: Starting the VMware VM...
-share: Waiting for machine to boot. This may take a few minutes...
-share: SSH address: 192.168.84.134:22
-share: SSH username: tc
-share: SSH auth method: password
-share:
-share: Inserting generated public key within guest...
-share: Removing insecure key from the guest if it's present...
-share: Key inserted! Disconnecting and reconnecting using new SSH key...
-share: Machine booted and ready!
-share: Forwarding ports...
-share: -- 31338 => 65534
-share: -- 22 => 2202
-share: SSH address: 192.168.84.134:22
-share: SSH username: tc
-share: SSH auth method: password
-share: Configuring network adapters within the VM...
-==> share:
-==> share: Your Vagrant Share is running! Name: bazaar_wolf:sultan_oasis
-==> share:
-==> share: You're sharing with SSH access. This means that another can SSH to
-==> share: your Vagrant machine by running:
-==> share:
-==> share:   vagrant connect --ssh bazaar_wolf:sultan_oasis
-==> share:
-```
-
-Anyone can then SSH directly to your Vagrant environment by running
-`vagrant connect --ssh NAME` where NAME is the name of the share outputted
-previously.
-
-```
-$ vagrant connect --ssh bazaar_wolf:sultan_oasis
-Loading share 'bazaar_wolf:sultan_oasis'...
-The SSH key to connect to this share is encrypted. You will
-require the password entered when creating the share to
-decrypt it. Verify you have access to this password before
-continuing.
-
-Press enter to continue, or Ctrl-C to exit now.
-Password for the private key:
-Executing SSH...
-Welcome to Ubuntu 12.04.3 LTS (GNU/Linux 3.8.0-29-generic x86_64)
-
- * Documentation:  https://help.ubuntu.com/
-Last login: Fri Mar  7 17:44:50 2014 from 192.168.163.1
-vagrant@vagrant:~$
-```
-
-If the private key is encrypted (the default behavior), then the connecting
-person will be prompted for the password to decrypt the private key.

data/vendor/bundle/ruby/2.4.0/bundler/gems/vagrant-04f7215b5e3f/website/source/docs/synced-folders/basic_usage.html.md

@@ -1,126 +0,0 @@
----
-layout: "docs"
-page_title: "Basic Usage - Synced Folders"
-sidebar_current: "syncedfolder-basic"
-description: |-
-  Synced folders are configured within your Vagrantfile using the
-  "config.vm.synced_folder" method.
----
-
-# Basic Usage
-
-## Configuration
-
-Synced folders are configured within your Vagrantfile using the
-`config.vm.synced_folder` method. Usage of the configuration directive
-is very simple:
-
-```ruby
-Vagrant.configure("2") do |config|
-  # other config here
-
-  config.vm.synced_folder "src/", "/srv/website"
-end
-```
-
-The first parameter is a path to a directory on the host machine. If
-the path is relative, it is relative to the project root. The second
-parameter must be an absolute path of where to share the folder within
-the guest machine. This folder will be created (recursively, if it must)
-if it does not exist.
-
-## Options
-
-You may also specify additional optional parameters when configuring
-synced folders. These options are listed below. More detailed examples of using
-some of these options are shown below this section, note the owner/group example
-supplies two additional options separated by commas.
-
-In addition to these options, the specific synced folder type might
-allow more options. See the documentation for your specific synced folder
-type for more details. The built-in synced folder types are documented
-in other pages available in the navigation for these docs.
-
-* `create` (boolean) - If true, the host path will be created if it
-  does not exist. Defaults to false.
-
-* `disabled` (boolean) - If true, this synced folder will be disabled and
-  will not be setup. This can be used to disable a previously defined synced
-  folder or to conditionally disable a definition based on some external
-  factor.
-
-* `group` (string) - The group that will own the synced folder. By default
-  this will be the SSH user. Some synced folder types do not support
-  modifying the group.
-
-* `mount_options` (array) - A list of additional mount options to pass
- to the `mount` command.
-
-* `owner` (string) - The user who should be the owner of this synced folder.
-  By default this will be the SSH user. Some synced folder types do not
-  support modifying the owner.
-
-* `type` (string) - The type of synced folder. If this is not specified,
-  Vagrant will automatically choose the best synced folder option for your
-  environment. Otherwise, you can specify a specific type such as "nfs".
-
-* `id` (string) - The name for the mount point of this synced folder in the
-  guest machine. This shows up when you run `mount` in the guest machine.
-
-## Enabling
-
-Synced folders are automatically setup during `vagrant up` and
-`vagrant reload`.
-
-## Disabling
-
-Synced folders can be disabled by adding the `disabled` option to
-any definition:
-
-```ruby
-Vagrant.configure("2") do |config|
-  config.vm.synced_folder "src/", "/srv/website", disabled: true
-end
-```
-
-Disabling the default `/vagrant` share can be done as follows:
-
-```ruby
-config.vm.synced_folder ".", "/vagrant", disabled: true
-```
-
-## Modifying the Owner/Group
-
-By default, Vagrant mounts the synced folders with the owner/group set
-to the SSH user. Sometimes it is preferable to mount folders with a different
-owner and group. It is possible to set these options:
-
-```ruby
-config.vm.synced_folder "src/", "/srv/website",
-  owner: "root", group: "root"
-```
-
-_NOTE: Owner and group IDs defined within `mount_options` will have precedence
-over the `owner` and `group` options._
-
-For example, given the following configuration:
-
-```ruby
-config.vm.synced_folder ".", "/vagrant", owner: "vagrant",
-  group: "vagrant", mount_options: ["uid=1234", "gid=1234"]
-```
-
-the mounted synced folder will be owned by the user with ID `1234` and the
-group with ID `1234`. The `owner` and `group` options will be ignored.
-
-## Symbolic Links
-
-Support for symbolic links across synced folder implementations and
-host/guest combinations is not consistent. Vagrant does its best to
-make sure symbolic links work by configuring various hypervisors (such
-as VirtualBox), but some host/guest combinations still do not work
-properly. This can affect some development environments that rely on
-symbolic links.
-
-The recommendation is to make sure to test symbolic links on all the
-host/guest combinations you sync folders on if this is important to you.