diff --git a/website/source/assets/stylesheets/_docs.scss b/website/source/assets/stylesheets/_docs.scss index bd2a52ed9..79971b491 100644 --- a/website/source/assets/stylesheets/_docs.scss +++ b/website/source/assets/stylesheets/_docs.scss @@ -9,11 +9,11 @@ body.layout-intro { } .equal-height { - display: -webkit-box; - display: -webkit-flex; - display: -ms-flexbox; - display: flex; - } + display: -webkit-box; + display: -webkit-flex; + display: -ms-flexbox; + display: flex; + } >.container { #main-content { diff --git a/website/source/assets/stylesheets/_mixins.scss b/website/source/assets/stylesheets/_mixins.scss index e90933d26..54385ea27 100644 --- a/website/source/assets/stylesheets/_mixins.scss +++ b/website/source/assets/stylesheets/_mixins.scss @@ -110,9 +110,9 @@ @mixin translate3d($x, $y: 0, $z: 0) { -webkit-transform: translate3d($x, $y, $z); - -moz-transform: translate3d($x, $y, $z); - -ms-transform: translate3d($x, $y, $z); - -o-transform: translate3d($x, $y, $z); + -moz-transform: translate3d($x, $y, $z); + -ms-transform: translate3d($x, $y, $z); + -o-transform: translate3d($x, $y, $z); } @mixin clearfix { diff --git a/website/source/assets/stylesheets/hashicorp-shared/_hashicorp-utility.scss b/website/source/assets/stylesheets/hashicorp-shared/_hashicorp-utility.scss index 2a353b0ed..244de1da4 100644 --- a/website/source/assets/stylesheets/hashicorp-shared/_hashicorp-utility.scss +++ b/website/source/assets/stylesheets/hashicorp-shared/_hashicorp-utility.scss @@ -7,7 +7,7 @@ // -------------------------------------------------- // Variables -$font-family-museo-sans: 'museo-sans', 'Helvetica Neue', Helvetica, Arial, sans-serif; +$font-family-museo-sans: 'museo-sans', 'Helvetica Neue', Helvetica, Arial, sans-serif; $header-font-family: $font-family-museo-sans; $header-font-weight: 600; // semi-bold diff --git a/website/source/community.html.erb b/website/source/community.html.erb index a2b3ea9b7..843548138 100644 --- a/website/source/community.html.erb +++ b/website/source/community.html.erb @@ -38,68 +38,68 @@ description: |-

- -
-

Mitchell Hashimoto (@mitchellh)

-

- Mitchell Hashimoto is a creator of Vagrant. He has been with the + +

+

Mitchell Hashimoto (@mitchellh)

+

+ Mitchell Hashimoto is a creator of Vagrant. He has been with the Vagrant project from the very beginning. Mitchell is also the creator of - Consul, - Packer, - Serf, and - Otto. -

-
+ Consul, + Packer, + Serf, and + Otto. +

+
- -
-

Jack Pearkes (@pearkes)

-

- Jack Pearkes created and maintains many projects at HashiCorp. He + +

+

Jack Pearkes (@pearkes)

+

+ Jack Pearkes created and maintains many projects at HashiCorp. He is the original author of Vagrant Cloud (now Atlas). He is also a core committer to Packer and maintains many successful - open source projects - while also being an employee of - HashiCorp. -

-
+ open source projects + while also being an employee of + HashiCorp. +

+
- -
-

Seth Vargo (@sethvargo)

-

+ +

+

Seth Vargo (@sethvargo)

+

Seth Vargo is a core committer to Vagrant, with his main focus being the core plugin system, pushes, and provisioners. Seth is also a contributor to Consul, Packer, and Vault, all while being an employee at HashiCorp. -

-
+

+
- -
-

Paul Hinze (@phinze)

-

- Paul Hinze is a contributor to Vagrant, with his main focus being - provisioners and working on HashiCorp's external plugins. He is + +

+

Paul Hinze (@phinze)

+

+ Paul Hinze is a contributor to Vagrant, with his main focus being + provisioners and working on HashiCorp's external plugins. He is also a core committer to Terraform, all while being an employee at HashiCorp. -

-
+

+
diff --git a/website/source/docs/cli/machine-readable.html.md b/website/source/docs/cli/machine-readable.html.md index e38c47898..e341f884c 100644 --- a/website/source/docs/cli/machine-readable.html.md +++ b/website/source/docs/cli/machine-readable.html.md @@ -90,72 +90,72 @@ with the machine-readable output. box-name - Name of a box installed into Vagrant. + Name of a box installed into Vagrant. box-provider - Provider for an installed box. + Provider for an installed box. cli-command - A subcommand of vagrant that is available. + A subcommand of vagrant that is available. error-exit - An error occurred that caused Vagrant to exit. This contains that - error. Contains two data elements: type of error, error message. + An error occurred that caused Vagrant to exit. This contains that + error. Contains two data elements: type of error, error message. provider-name - The provider name of the target machine. - targeted + The provider name of the target machine. + targeted ssh-config - The OpenSSH compatible SSH config for a machine. This is usually + The OpenSSH compatible SSH config for a machine. This is usually the result of the "ssh-config" command. - targeted + targeted state - The state ID of the target machine. - targeted + The state ID of the target machine. + targeted state-human-long - Human-readable description of the state of the machine. This is the - long version, and may be a paragraph or longer. - targeted + Human-readable description of the state of the machine. This is the + long version, and may be a paragraph or longer. + targeted state-human-short - Human-readable description of the state of the machine. This is the - short version, limited to at most a sentence. - targeted + Human-readable description of the state of the machine. This is the + short version, limited to at most a sentence. + targeted diff --git a/website/source/docs/cli/package.html.md b/website/source/docs/cli/package.html.md index 87a2ad8be..1dd310fab 100644 --- a/website/source/docs/cli/package.html.md +++ b/website/source/docs/cli/package.html.md @@ -36,10 +36,10 @@ be made by hand. when the resulting box is used.
- A common misconception is that the --vagrantfile - option will package a Vagrantfile that is used when vagrant init - 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 - Vagrantfile load order. + A common misconception is that the --vagrantfile + option will package a Vagrantfile that is used when vagrant init + 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 + Vagrantfile load order.
diff --git a/website/source/docs/docker/basics.html.md b/website/source/docs/docker/basics.html.md index 85f1d3e17..6d007c412 100644 --- a/website/source/docs/docker/basics.html.md +++ b/website/source/docs/docker/basics.html.md @@ -95,11 +95,11 @@ to more closely match production by running a VM running Ubuntu, RHEL, etc. It can run any operating system supported by Vagrant.
- Synced folder note: 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. + Synced folder note: 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.
An example of changing the host VM is shown below. Remember that this diff --git a/website/source/docs/docker/index.html.md b/website/source/docs/docker/index.html.md index 286e6d9b5..4c57d0cd9 100644 --- a/website/source/docs/docker/index.html.md +++ b/website/source/docs/docker/index.html.md @@ -3,10 +3,10 @@ layout: "docs" page_title: "Docker Provider" sidebar_current: "providers-docker" description: |- - Vagrant comes with support out of the box for - using Docker as a provider. This allows for your development environments - to be backed by Docker containers rather than virtual machines. Additionally, - it provides for a good workflow for developing Dockerfiles. + Vagrant comes with support out of the box for + using Docker as a provider. This allows for your development environments + to be backed by Docker containers rather than virtual machines. Additionally, + it provides for a good workflow for developing Dockerfiles. --- # Docker @@ -17,10 +17,10 @@ to be backed by Docker containers rather than virtual machines. Additionally, it provides for a good workflow for developing Dockerfiles.
- Warning: Docker knowledge assumed. We assume that - you know what Docker is and that you are comfortable with the basics - of Docker. If not, we recommend starting with another provider such - as VirtualBox. + Warning: Docker knowledge assumed. We assume that + you know what Docker is and that you are comfortable with the basics + of Docker. If not, we recommend starting with another provider such + as VirtualBox.
Use the navigation to the left to find a specific Docker topic diff --git a/website/source/docs/hyperv/boxes.html.md b/website/source/docs/hyperv/boxes.html.md index d3a273326..3c4eabe60 100644 --- a/website/source/docs/hyperv/boxes.html.md +++ b/website/source/docs/hyperv/boxes.html.md @@ -3,8 +3,8 @@ layout: "docs" page_title: "Creating a Base Box - Hyper-V Provider" sidebar_current: "providers-hyperv-boxes" description: |- - As with every Vagrant provider, the Vagrant Hyper-V provider has a custom box - format that affects how base boxes are made. + As with every Vagrant provider, the Vagrant Hyper-V provider has a custom box + format that affects how base boxes are made. --- # Creating a Base Box @@ -23,11 +23,11 @@ Additionally, it is helpful to understand the [basics of the box file format](/docs/boxes/format.html).
- Advanced topic! This is a reasonably advanced topic that - a beginning user of Vagrant does not need to understand. If you are - just getting started with Vagrant, skip this and use an available - box. If you are an experienced user of Vagrant and want to create - your own custom boxes, this is for you. + Advanced topic! This is a reasonably advanced topic that + a beginning user of Vagrant does not need to understand. If you are + just getting started with Vagrant, skip this and use an available + box. If you are an experienced user of Vagrant and want to create + your own custom boxes, this is for you.
## Additional Software diff --git a/website/source/docs/hyperv/configuration.html.md b/website/source/docs/hyperv/configuration.html.md index 630cbb124..86c77c8eb 100644 --- a/website/source/docs/hyperv/configuration.html.md +++ b/website/source/docs/hyperv/configuration.html.md @@ -19,8 +19,8 @@ you may set. A complete reference is shown below: * `memory` (integer) - Number of MegaBytes allocated to VM at startup. Defaults is taken from box image XML. * `maxmemory` (integer) - Number of MegaBytes maximal allowed to allocate for VM - This parameter is switch on Dynamic Allocation of memory. - Defaults is taken from box image XML. + This parameter is switch on Dynamic Allocation of memory. + Defaults is taken from box image XML. * `vlan_id` (integer) - Number of Vlan ID for your guest network interface Defaults is not defined, vlan configuration will be untouched if not set. * `mac` (string) - MAC address for your guest network interface diff --git a/website/source/docs/installation/index.html.md b/website/source/docs/installation/index.html.md index 8fe692e5d..196a98dee 100644 --- a/website/source/docs/installation/index.html.md +++ b/website/source/docs/installation/index.html.md @@ -3,9 +3,9 @@ layout: "docs" page_title: "Installing Vagrant" sidebar_current: "installation" description: |- - Installing Vagrant is extremely easy. Head over to the Vagrant downloads page - and get the appropriate installer or package for your platform. Install the - package using standard procedures for your operating system. + Installing Vagrant is extremely easy. Head over to the Vagrant downloads page + and get the appropriate installer or package for your platform. Install the + package using standard procedures for your operating system. --- # Installing Vagrant @@ -21,18 +21,18 @@ logging out and logging back in to your system (this is particularly necessary sometimes for Windows). diff --git a/website/source/docs/networking/index.html.md b/website/source/docs/networking/index.html.md index 3acbf5787..6efc110f1 100644 --- a/website/source/docs/networking/index.html.md +++ b/website/source/docs/networking/index.html.md @@ -3,9 +3,9 @@ layout: "docs" page_title: "Networking" sidebar_current: "networking" description: |- - In order to access the Vagrant environment created, Vagrant exposes - some high-level networking options for things such as forwarded ports, - connecting to a public network, or creating a private network. + In order to access the Vagrant environment created, Vagrant exposes + some high-level networking options for things such as forwarded ports, + connecting to a public network, or creating a private network. --- # Networking @@ -34,9 +34,9 @@ to do this, so please read the documentation for your specific provider to see what options are available.
- For beginners: It is strongly recommended you use - only the high-level networking options until you are comfortable - with the Vagrant workflow and have things working at a basic level. - Provider-specific network configuration can very quickly lock you out - of your guest machine if improperly done. + For beginners: It is strongly recommended you use + only the high-level networking options until you are comfortable + with the Vagrant workflow and have things working at a basic level. + Provider-specific network configuration can very quickly lock you out + of your guest machine if improperly done.
diff --git a/website/source/docs/networking/private_network.html.md b/website/source/docs/networking/private_network.html.md index 3f239f465..01324cc77 100644 --- a/website/source/docs/networking/private_network.html.md +++ b/website/source/docs/networking/private_network.html.md @@ -3,9 +3,9 @@ layout: "docs" page_title: "Private Networks - Networking" sidebar_current: "networking-private" description: |- - Vagrant private networks allow you to access your guest machine by some - address that is not publicly accessible from the global internet. In general, - this means your machine gets an address in the private address space. + Vagrant private networks allow you to access your guest machine by some + address that is not publicly accessible from the global internet. In general, + this means your machine gets an address in the private address space. --- # Private Networks @@ -21,13 +21,13 @@ restriction that they're backed by the same [provider](/docs/providers/)) can communicate with each other on private networks.
- Guest operating system support. Private networks - generally require configuring the network adapters on the guest - machine. This process varies from OS to OS. Vagrant ships with - knowledge of how to configure networks on a variety of guest - operating systems, but it is possible if you are using a particularly - old or new operating system that private networks will not properly - configure. + Guest operating system support. Private networks + generally require configuring the network adapters on the guest + machine. This process varies from OS to OS. Vagrant ships with + knowledge of how to configure networks on a variety of guest + operating systems, but it is possible if you are using a particularly + old or new operating system that private networks will not properly + configure.
## DHCP @@ -70,9 +70,9 @@ For some operating systems, additional configuration options for the static IP address are available such as setting the default gateway or MTU.
- Warning! Do not choose an IP that overlaps with any - other IP space on your system. This can cause the network to not be - reachable. + Warning! Do not choose an IP that overlaps with any + other IP space on your system. This can cause the network to not be + reachable.
## IPv6 diff --git a/website/source/docs/networking/public_network.html.md b/website/source/docs/networking/public_network.html.md index 057136d3c..bcab15d1d 100644 --- a/website/source/docs/networking/public_network.html.md +++ b/website/source/docs/networking/public_network.html.md @@ -3,10 +3,10 @@ layout: "docs" page_title: "Public Networks - Networking" sidebar_current: "networking-public" description: |- - Vagrant public networks are less private than private networks, and the exact - meaning actually varies from provider to provider, hence the ambiguous - definition. The idea is that while private networks should never allow the - general public access to your machine, public networks can. + Vagrant public networks are less private than private networks, and the exact + meaning actually varies from provider to provider, hence the ambiguous + definition. The idea is that while private networks should never allow the + general public access to your machine, public networks can. --- # Public Networks @@ -20,22 +20,22 @@ hence the ambiguous definition. The idea is that while general public access to your machine, public networks can.
- Confused? We kind of are, too. It is likely that - public networks will be replaced by :bridged in a - future release, since that is in general what should be done with - public networks, and providers that do not support bridging generally - do not have any other features that map to public networks either. + Confused? We kind of are, too. It is likely that + public networks will be replaced by :bridged in a + future release, since that is in general what should be done with + public networks, and providers that do not support bridging generally + do not have any other features that map to public networks either.
- Warning! Vagrant boxes are insecure by default - and by design, featuring public passwords, insecure keypairs - for SSH access, and potentially allow root access over SSH. With - these known credentials, your box is easily accessible by anyone on - your network. Before configuring Vagrant to use a public network, - consider all potential security implications - and review the default box - configuration to identify potential security risks. + Warning! Vagrant boxes are insecure by default + and by design, featuring public passwords, insecure keypairs + for SSH access, and potentially allow root access over SSH. With + these known credentials, your box is easily accessible by anyone on + your network. Before configuring Vagrant to use a public network, + consider all potential security implications + and review the default box + configuration to identify potential security risks.
## DHCP diff --git a/website/source/docs/plugins/commands.html.md b/website/source/docs/plugins/commands.html.md index 414e2b13d..1c5038593 100644 --- a/website/source/docs/plugins/commands.html.md +++ b/website/source/docs/plugins/commands.html.md @@ -3,9 +3,9 @@ layout: "docs" page_title: "Command Plugins - Plugin Development" sidebar_current: "plugins-commands" description: |- - This page documents how to add new commands to Vagrant, invokable - via "vagrant YOUR-COMMAND". Prior to reading this, you should be familiar - with the plugin development basics. + This page documents how to add new commands to Vagrant, invokable + via "vagrant YOUR-COMMAND". Prior to reading this, you should be familiar + with the plugin development basics. --- # Plugin Development: Commands @@ -15,9 +15,9 @@ via `vagrant YOUR-COMMAND`. Prior to reading this, you should be familiar with the [plugin development basics](/docs/plugins/development-basics.html).
- Warning: Advanced Topic! Developing plugins is an - advanced topic that only experienced Vagrant users who are reasonably - comfortable with Ruby should approach. + Warning: Advanced Topic! Developing plugins is an + advanced topic that only experienced Vagrant users who are reasonably + comfortable with Ruby should approach.
## Definition Component diff --git a/website/source/docs/plugins/configuration.html.md b/website/source/docs/plugins/configuration.html.md index 8b8d1fc8a..3d1bd8dcb 100644 --- a/website/source/docs/plugins/configuration.html.md +++ b/website/source/docs/plugins/configuration.html.md @@ -3,9 +3,9 @@ layout: "docs" page_title: "Custom Configuration - Plugin Development" sidebar_current: "plugins-configuration" description: |- - This page documents how to add new configuration options to Vagrant, - settable with "config.YOURKEY" in Vagrantfiles. Prior to reading this, - you should be familiar with the plugin development basics. + This page documents how to add new configuration options to Vagrant, + settable with "config.YOURKEY" in Vagrantfiles. Prior to reading this, + you should be familiar with the plugin development basics. --- # Plugin Development: Configuration @@ -16,9 +16,9 @@ you should be familiar with the [plugin development basics](/docs/plugins/development-basics.html).
- Warning: Advanced Topic! Developing plugins is an - advanced topic that only experienced Vagrant users who are reasonably - comfortable with Ruby should approach. + Warning: Advanced Topic! Developing plugins is an + advanced topic that only experienced Vagrant users who are reasonably + comfortable with Ruby should approach.
## Definition Component diff --git a/website/source/docs/plugins/development-basics.html.md b/website/source/docs/plugins/development-basics.html.md index 5f826d118..ec18507af 100644 --- a/website/source/docs/plugins/development-basics.html.md +++ b/website/source/docs/plugins/development-basics.html.md @@ -3,10 +3,10 @@ layout: "docs" page_title: "Plugin Development Basics - Plugins" sidebar_current: "plugins-development-basics" description: |- - Plugins are a great way to augment or change the behavior and functionality - of Vagrant. Since plugins introduce additional external dependencies for - users, they should be used as a last resort when attempting to - do something with Vagrant. + Plugins are a great way to augment or change the behavior and functionality + of Vagrant. Since plugins introduce additional external dependencies for + users, they should be used as a last resort when attempting to + do something with Vagrant. --- # Plugin Development Basics @@ -21,9 +21,9 @@ into Vagrant, plugins are the best way, since they are safe against future upgrades and use a stable API.
- Warning: Advanced Topic! Developing plugins is an - advanced topic that only experienced Vagrant users who are reasonably - comfortable with Ruby should approach. + Warning: Advanced Topic! Developing plugins is an + advanced topic that only experienced Vagrant users who are reasonably + comfortable with Ruby should approach.
Plugins are written using [Ruby](http://www.ruby-lang.org/en/) and are packaged diff --git a/website/source/docs/plugins/guest-capabilities.html.md b/website/source/docs/plugins/guest-capabilities.html.md index b43bd2935..104bcd454 100644 --- a/website/source/docs/plugins/guest-capabilities.html.md +++ b/website/source/docs/plugins/guest-capabilities.html.md @@ -3,10 +3,10 @@ layout: "docs" page_title: "Guest Capabilities - Plugin Development" sidebar_current: "plugins-guestcapabilities" description: |- - This page documents how to add new capabilities for guests to Vagrant, - allowing Vagrant to perform new actions on specific guest operating systems. - Prior to reading this, you should be familiar with the plugin development - basics. + This page documents how to add new capabilities for guests to Vagrant, + allowing Vagrant to perform new actions on specific guest operating systems. + Prior to reading this, you should be familiar with the plugin development + basics. --- # Plugin Development: Guest Capabilities @@ -18,9 +18,9 @@ Prior to reading this, you should be familiar with the [plugin development basics](/docs/plugins/development-basics.html).
- Warning: Advanced Topic! Developing plugins is an - advanced topic that only experienced Vagrant users who are reasonably - comfortable with Ruby should approach. + Warning: Advanced Topic! Developing plugins is an + advanced topic that only experienced Vagrant users who are reasonably + comfortable with Ruby should approach.
Guest capabilities augment [guests](/docs/plugins/guests.html) by attaching diff --git a/website/source/docs/plugins/guests.html.md b/website/source/docs/plugins/guests.html.md index e0a94e603..7b5feab43 100644 --- a/website/source/docs/plugins/guests.html.md +++ b/website/source/docs/plugins/guests.html.md @@ -3,9 +3,9 @@ layout: "docs" page_title: "Custom Guests - Plugin Development" sidebar_current: "plugins-guests" description: |- - This page documents how to add new guest OS detection to Vagrant, allowing - Vagrant to properly configure new operating systems. Prior to reading this, - you should be familiar with the plugin development basics. + This page documents how to add new guest OS detection to Vagrant, allowing + Vagrant to properly configure new operating systems. Prior to reading this, + you should be familiar with the plugin development basics. --- # Plugin Development: Guests @@ -16,9 +16,9 @@ Prior to reading this, you should be familiar with the [plugin development basics](/docs/plugins/development-basics.html).
- Warning: Advanced Topic! Developing plugins is an - advanced topic that only experienced Vagrant users who are reasonably - comfortable with Ruby should approach. + Warning: Advanced Topic! Developing plugins is an + advanced topic that only experienced Vagrant users who are reasonably + comfortable with Ruby should approach.
Vagrant has many features that requires doing guest OS-specific diff --git a/website/source/docs/plugins/host-capabilities.html.md b/website/source/docs/plugins/host-capabilities.html.md index a3245a446..d458a550e 100644 --- a/website/source/docs/plugins/host-capabilities.html.md +++ b/website/source/docs/plugins/host-capabilities.html.md @@ -3,7 +3,7 @@ layout: "docs" page_title: "Host Capabilities - Plugin Development" sidebar_current: "plugins-hostcapabilities" description: |- - This page documents how to add new capabilities for hosts to Vagrant, allowing Vagrant to perform new actions on specific host operating systems. Prior to reading this, you should be familiar with the plugin development basics. + This page documents how to add new capabilities for hosts to Vagrant, allowing Vagrant to perform new actions on specific host operating systems. Prior to reading this, you should be familiar with the plugin development basics. --- # Plugin Development: Host Capabilities @@ -15,9 +15,9 @@ Prior to reading this, you should be familiar with the [plugin development basics](/docs/plugins/development-basics.html).
- Warning: Advanced Topic! Developing plugins is an - advanced topic that only experienced Vagrant users who are reasonably - comfortable with Ruby should approach. + Warning: Advanced Topic! Developing plugins is an + advanced topic that only experienced Vagrant users who are reasonably + comfortable with Ruby should approach.
Host capabilities augment [hosts](/docs/plugins/hosts.html) by attaching diff --git a/website/source/docs/plugins/hosts.html.md b/website/source/docs/plugins/hosts.html.md index f596389c1..96dc6fc4b 100644 --- a/website/source/docs/plugins/hosts.html.md +++ b/website/source/docs/plugins/hosts.html.md @@ -3,10 +3,10 @@ layout: "docs" page_title: "Custom Hosts - Plugin Development" sidebar_current: "plugins-hosts" description: |- - This page documents how to add new host OS detection to Vagrant, allowing - Vagrant to properly execute host-specific operations on new operating systems. - Prior to reading this, you should be familiar with the plugin development - basics. + This page documents how to add new host OS detection to Vagrant, allowing + Vagrant to properly execute host-specific operations on new operating systems. + Prior to reading this, you should be familiar with the plugin development + basics. --- # Plugin Development: Hosts @@ -17,9 +17,9 @@ Prior to reading this, you should be familiar with the [plugin development basics](/docs/plugins/development-basics.html).
- Warning: Advanced Topic! Developing plugins is an - advanced topic that only experienced Vagrant users who are reasonably - comfortable with Ruby should approach. + Warning: Advanced Topic! Developing plugins is an + advanced topic that only experienced Vagrant users who are reasonably + comfortable with Ruby should approach.
Vagrant has some features that require host OS-specific actions, such as diff --git a/website/source/docs/plugins/packaging.html.md b/website/source/docs/plugins/packaging.html.md index 22c6d27d1..f0fe7a453 100644 --- a/website/source/docs/plugins/packaging.html.md +++ b/website/source/docs/plugins/packaging.html.md @@ -3,10 +3,10 @@ layout: "docs" page_title: "Packaging and Distribution - Plugin Development" sidebar_current: "plugins-packaging" description: |- - This page documents how to organize the file structure of your plugin - and distribute it so that it is installable using standard installation - methods. Prior to reading this, you should be familiar with the plugin - development basics. + This page documents how to organize the file structure of your plugin + and distribute it so that it is installable using standard installation + methods. Prior to reading this, you should be familiar with the plugin + development basics. --- # Plugin Development: Packaging & Distribution @@ -18,9 +18,9 @@ Prior to reading this, you should be familiar with the [plugin development basics](/docs/plugins/development-basics.html).
- Warning: Advanced Topic! Developing plugins is an - advanced topic that only experienced Vagrant users who are reasonably - comfortable with Ruby should approach. + Warning: Advanced Topic! Developing plugins is an + advanced topic that only experienced Vagrant users who are reasonably + comfortable with Ruby should approach.
## Example Plugin @@ -48,11 +48,11 @@ dependencies and change any metadata. View the [vagrant-aws.gemspec](https://git for a good example.
-

- Do not depend on Vagrant for your gem. Vagrant - is no longer distributed as a gem, and you can assume that it will - always be available when your plugin is installed. -

+

+ Do not depend on Vagrant for your gem. Vagrant + is no longer distributed as a gem, and you can assume that it will + always be available when your plugin is installed. +

Once the directory structure for a RubyGem is setup, you will want diff --git a/website/source/docs/plugins/providers.html.md b/website/source/docs/plugins/providers.html.md index 206f66eda..9ff0a65bd 100644 --- a/website/source/docs/plugins/providers.html.md +++ b/website/source/docs/plugins/providers.html.md @@ -3,10 +3,10 @@ layout: "docs" page_title: "Custom Providers - Plugin Development" sidebar_current: "plugins-providers" description: |- - This page documents how to add support for new providers to Vagrant, allowing - Vagrant to run and manage machines powered by a system other than VirtualBox. - Prior to reading this, you should be familiar with the plugin development - basics. + This page documents how to add support for new providers to Vagrant, allowing + Vagrant to run and manage machines powered by a system other than VirtualBox. + Prior to reading this, you should be familiar with the plugin development + basics. --- # Plugin Development: Providers @@ -21,9 +21,9 @@ Prior to developing a provider you should also be familiar with how a user standpoint.
- Warning: Advanced Topic! Developing plugins is an - advanced topic that only experienced Vagrant users who are reasonably - comfortable with Ruby should approach. + Warning: Advanced Topic! Developing plugins is an + advanced topic that only experienced Vagrant users who are reasonably + comfortable with Ruby should approach.
## Example Provider: AWS @@ -204,12 +204,12 @@ via the `provider_config` attribute. So within actions or your provider class, you can access the config via `machine.provider_config`.
- Best practice: Your provider should not require - provider-specific configuration to function, if possible. Vagrant - practices a strong convention over configuration - philosophy. When a user installs your provider, they should ideally - be able to vagrant up --provider=your_provider and - have it just work. + Best practice: Your provider should not require + provider-specific configuration to function, if possible. Vagrant + practices a strong convention over configuration + philosophy. When a user installs your provider, they should ideally + be able to vagrant up --provider=your_provider and + have it just work.
## Parallelization diff --git a/website/source/docs/plugins/provisioners.html.md b/website/source/docs/plugins/provisioners.html.md index 8f2ebcd9f..6fbc730b8 100644 --- a/website/source/docs/plugins/provisioners.html.md +++ b/website/source/docs/plugins/provisioners.html.md @@ -3,10 +3,10 @@ layout: "docs" page_title: "Custom Provisioners - Plugin Development" sidebar_current: "plugins-provisioners" script: |- - This page documents how to add new provisioners to Vagrant, allowing Vagrant - to automatically install software and configure software using a custom - provisioner. Prior to reading this, you should be familiar with the plugin - development basics. + This page documents how to add new provisioners to Vagrant, allowing Vagrant + to automatically install software and configure software using a custom + provisioner. Prior to reading this, you should be familiar with the plugin + development basics. --- # Plugin Development: Provisioners @@ -17,9 +17,9 @@ using a custom provisioner. Prior to reading this, you should be familiar with the [plugin development basics](/docs/plugins/development-basics.html).
- Warning: Advanced Topic! Developing plugins is an - advanced topic that only experienced Vagrant users who are reasonably - comfortable with Ruby should approach. + Warning: Advanced Topic! Developing plugins is an + advanced topic that only experienced Vagrant users who are reasonably + comfortable with Ruby should approach.
## Definition Component diff --git a/website/source/docs/plugins/usage.html.md b/website/source/docs/plugins/usage.html.md index fb0b02497..5334a119a 100644 --- a/website/source/docs/plugins/usage.html.md +++ b/website/source/docs/plugins/usage.html.md @@ -3,8 +3,8 @@ layout: "docs" page_title: "Plugin Usage - Plugins" sidebar_current: "plugins-usage" description: |- - Installing a Vagrant plugin is easy, and should not take more than a few - seconds. + Installing a Vagrant plugin is easy, and should not take more than a few + seconds. --- # Plugin Usage @@ -16,8 +16,8 @@ more information on how to use it, but there is one common method for installation and plugin activation.
- Warning! 3rd party plugins can introduce instabilities - into Vagrant due to the nature of them being written by non-core users. + Warning! 3rd party plugins can introduce instabilities + into Vagrant due to the nature of them being written by non-core users.
## Installation diff --git a/website/source/docs/providers/basic_usage.html.md b/website/source/docs/providers/basic_usage.html.md index eb550abe1..19c6dc337 100644 --- a/website/source/docs/providers/basic_usage.html.md +++ b/website/source/docs/providers/basic_usage.html.md @@ -57,11 +57,11 @@ see what provider is backing a running machine, so commands such as `destroy`, `suspend`, etc. do not need to be told what provider to use.
- Vagrant currently restricts you to bringing up one provider per machine. - If you have a multi-machine environment, you can bring up one machine - backed by VirtualBox and another backed by VMware Fusion, for example, but you - cannot back the same machine with both VirtualBox and - VMware Fusion. This is a limitation that will be removed in a future + Vagrant currently restricts you to bringing up one provider per machine. + If you have a multi-machine environment, you can bring up one machine + backed by VirtualBox and another backed by VMware Fusion, for example, but you + cannot back the same machine with both VirtualBox and + VMware Fusion. This is a limitation that will be removed in a future version of Vagrant.
diff --git a/website/source/docs/providers/configuration.html.md b/website/source/docs/providers/configuration.html.md index 0af811474..1d80c832d 100644 --- a/website/source/docs/providers/configuration.html.md +++ b/website/source/docs/providers/configuration.html.md @@ -83,9 +83,9 @@ In the above case, Vagrant will use the "precise64" box by default, but will use "precise64_fusion" if the VMware Fusion provider is used.
- The Vagrant Way: The proper "Vagrant way" is to - avoid any provider-specific overrides if possible by making boxes - for multiple providers that are as identical as possible, since box - names can map to multiple providers. However, this is not always possible, - and in those cases, overrides are available. + The Vagrant Way: The proper "Vagrant way" is to + avoid any provider-specific overrides if possible by making boxes + for multiple providers that are as identical as possible, since box + names can map to multiple providers. However, this is not always possible, + and in those cases, overrides are available.
diff --git a/website/source/docs/provisioning/cfengine.html.md b/website/source/docs/provisioning/cfengine.html.md index 0044740a7..f4fab515b 100644 --- a/website/source/docs/provisioning/cfengine.html.md +++ b/website/source/docs/provisioning/cfengine.html.md @@ -3,10 +3,10 @@ layout: "docs" page_title: "CFEngine Provisioner" sidebar_current: "provisioning-cfengine" description: |- - The Vagrant CFEngine provisioner allows you to provision the guest using - CFEngine. It can set up both CFEngine policy servers and clients. You can - configure both the policy server and the clients in a single multi-machine - Vagrantfile. + The Vagrant CFEngine provisioner allows you to provision the guest using + CFEngine. It can set up both CFEngine policy servers and clients. You can + configure both the policy server and the clients in a single multi-machine + Vagrantfile. --- # CFEngine Provisioner @@ -20,9 +20,9 @@ and the clients in a single [multi-machine `Vagrantfile`](/docs/multi-machine/).
- Warning: If you are not familiar with CFEngine and Vagrant already, - I recommend starting with the shell - provisioner. However, if you are comfortable with Vagrant + Warning: If you are not familiar with CFEngine and Vagrant already, + I recommend starting with the shell + provisioner. However, if you are comfortable with Vagrant already, Vagrant is the best way to learn CFEngine.
diff --git a/website/source/docs/provisioning/chef_client.html.md b/website/source/docs/provisioning/chef_client.html.md index 97c7053ee..aeabf3318 100644 --- a/website/source/docs/provisioning/chef_client.html.md +++ b/website/source/docs/provisioning/chef_client.html.md @@ -3,9 +3,9 @@ layout: "docs" page_title: "Chef Client - Provisioning" sidebar_current: "provisioning-chefclient" description: |- - The Vagrant Chef Client provisioner allows you to provision the guest using - Chef, specifically by connecting to an existing Chef Server and registering - the Vagrant machine as a node within your infrastructure. + The Vagrant Chef Client provisioner allows you to provision the guest using + Chef, specifically by connecting to an existing Chef Server and registering + the Vagrant machine as a node within your infrastructure. --- # Chef Client Provisioner @@ -22,9 +22,9 @@ to start with the [Chef Solo](/docs/provisioning/chef_solo.html) provisioner.
- Warning: If you are not familiar with Chef and Vagrant already, - I recommend starting with the shell - provisioner. + Warning: If you are not familiar with Chef and Vagrant already, + I recommend starting with the shell + provisioner.
## Authenticating diff --git a/website/source/docs/provisioning/chef_solo.html.md b/website/source/docs/provisioning/chef_solo.html.md index 03273416a..f140a2182 100644 --- a/website/source/docs/provisioning/chef_solo.html.md +++ b/website/source/docs/provisioning/chef_solo.html.md @@ -3,8 +3,8 @@ layout: "docs" page_title: "Chef Solo - Provisioning" sidebar_current: "provisioning-chefsolo" description: |- - The Vagrant Chef Solo provisioner allows you to provision the guest using - Chef, specifically with chef-solo. + The Vagrant Chef Solo provisioner allows you to provision the guest using + Chef, specifically with chef-solo. --- # Chef Solo Provisioner @@ -22,10 +22,10 @@ Chef cookbooks, since Chef is a complete system that is beyond the scope of a single page of documentation.
- Warning: If you are not familiar with Chef and Vagrant already, - I recommend starting with the shell - provisioner. However, if you are comfortable with Vagrant already, Vagrant - is the best way to learn Chef. + Warning: If you are not familiar with Chef and Vagrant already, + I recommend starting with the shell + provisioner. However, if you are comfortable with Vagrant already, Vagrant + is the best way to learn Chef.
## Options diff --git a/website/source/docs/provisioning/chef_zero.html.md b/website/source/docs/provisioning/chef_zero.html.md index d445315ab..b5ef96174 100644 --- a/website/source/docs/provisioning/chef_zero.html.md +++ b/website/source/docs/provisioning/chef_zero.html.md @@ -3,8 +3,8 @@ layout: "docs" page_title: "Chef Zero - Provisioning" sidebar_current: "provisioning-chefzero" description: |- -The Vagrant Chef Zero provisioner allows you to provision the guest using -Chef, specifically with chef-zero. + The Vagrant Chef Zero provisioner allows you to provision the guest using + Chef, specifically with chef-zero. --- # Chef Zero Provisioner diff --git a/website/source/docs/provisioning/docker.html.md b/website/source/docs/provisioning/docker.html.md index 10c053b2e..47b69f487 100644 --- a/website/source/docs/provisioning/docker.html.md +++ b/website/source/docs/provisioning/docker.html.md @@ -3,8 +3,8 @@ layout: "docs" page_title: "Docker - Provisioning" sidebar_current: "provisioning-docker" description: |- - The Vagrant Docker provisioner can automatically install Docker, pull Docker - containers, and configure certain containers to run on boot. + The Vagrant Docker provisioner can automatically install Docker, pull Docker + containers, and configure certain containers to run on boot. --- # Docker Provisioner @@ -29,10 +29,10 @@ your application runtime. You can use the Puppet provisioner along with the Docker provisioner.
- Note: This documentation is for the Docker + Note: This documentation is for the Docker provisioner. If you are looking for the Docker - provider, visit the - Docker provider documentation. + provider, visit the + Docker provider documentation.
## Options diff --git a/website/source/docs/provisioning/puppet_agent.html.md b/website/source/docs/provisioning/puppet_agent.html.md index d0cfeff4a..facca6e4a 100644 --- a/website/source/docs/provisioning/puppet_agent.html.md +++ b/website/source/docs/provisioning/puppet_agent.html.md @@ -3,9 +3,9 @@ layout: "docs" page_title: "Puppet Agent - Provisioning" sidebar_current: "provisioning-puppetagent" description: |- - The Vagrant Puppet agent provisioner allows you to provision the guest using - Puppet, specifically by calling "puppet agent", connecting to a Puppet master, - and retrieving the set of modules and manifests from there. + The Vagrant Puppet agent provisioner allows you to provision the guest using + Puppet, specifically by calling "puppet agent", connecting to a Puppet master, + and retrieving the set of modules and manifests from there. --- # Puppet Agent Provisioner @@ -18,10 +18,10 @@ calling `puppet agent`, connecting to a Puppet master, and retrieving the set of modules and manifests from there.
- Warning: If you are not familiar with Puppet and Vagrant already, - I recommend starting with the shell - provisioner. However, if you are comfortable with Vagrant already, Vagrant - is the best way to learn Puppet. + Warning: If you are not familiar with Puppet and Vagrant already, + I recommend starting with the shell + provisioner. However, if you are comfortable with Vagrant already, Vagrant + is the best way to learn Puppet.
## Options diff --git a/website/source/docs/provisioning/puppet_apply.html.md b/website/source/docs/provisioning/puppet_apply.html.md index 49ba94b5a..9daf88c41 100644 --- a/website/source/docs/provisioning/puppet_apply.html.md +++ b/website/source/docs/provisioning/puppet_apply.html.md @@ -3,8 +3,8 @@ layout: "docs" page_title: "Puppet Apply - Provisioning" sidebar_current: "provisioning-puppetapply" description: |- - The Vagrant Puppet provisioner allows you to provision the guest using - Puppet, specifically by calling "puppet apply", without a Puppet Master. + The Vagrant Puppet provisioner allows you to provision the guest using + Puppet, specifically by calling "puppet apply", without a Puppet Master. --- # Puppet Apply Provisioner @@ -16,10 +16,10 @@ The Vagrant Puppet provisioner allows you to provision the guest using calling `puppet apply`, without a Puppet Master.
- Warning: If you are not familiar with Puppet and Vagrant already, - I recommend starting with the shell - provisioner. However, if you are comfortable with Vagrant already, Vagrant - is the best way to learn Puppet. + Warning: If you are not familiar with Puppet and Vagrant already, + I recommend starting with the shell + provisioner. However, if you are comfortable with Vagrant already, Vagrant + is the best way to learn Puppet.
## Options diff --git a/website/source/docs/share/provider.html.md b/website/source/docs/share/provider.html.md index de849e414..b0c6cefcd 100644 --- a/website/source/docs/share/provider.html.md +++ b/website/source/docs/share/provider.html.md @@ -3,16 +3,16 @@ 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. + 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
- Warning: Advanced Topic! 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. + Warning: Advanced Topic! 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.
If you are developing a [custom Vagrant provider](/docs/plugins/providers.html), @@ -22,7 +22,7 @@ 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`. + 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`. diff --git a/website/source/docs/synced-folders/nfs.html.md b/website/source/docs/synced-folders/nfs.html.md index d9765006b..72c034ee3 100644 --- a/website/source/docs/synced-folders/nfs.html.md +++ b/website/source/docs/synced-folders/nfs.html.md @@ -3,11 +3,11 @@ layout: "docs" page_title: "NFS - Synced Folders" sidebar_current: "syncedfolder-nfs" description: |- - In some cases the default shared folder implementations such as VirtualBox - shared folders have high performance penalties. If you are seeing less than - ideal performance with synced folders, NFS can offer a solution. Vagrant has - built-in support to orchestrate the configuration of the NFS server on the host - and guest for you. + In some cases the default shared folder implementations such as VirtualBox + shared folders have high performance penalties. If you are seeing less than + ideal performance with synced folders, NFS can offer a solution. Vagrant has + built-in support to orchestrate the configuration of the NFS server on the host + and guest for you. --- # NFS @@ -19,9 +19,9 @@ can offer a solution. Vagrant has built-in support to orchestrate the configuration of the NFS server on the host and guest for you.
- Windows users: NFS folders do not work on Windows - hosts. Vagrant will ignore your request for NFS synced folders on - Windows. + Windows users: NFS folders do not work on Windows + hosts. Vagrant will ignore your request for NFS synced folders on + Windows.
## Prerequisites diff --git a/website/source/docs/synced-folders/smb.html.md b/website/source/docs/synced-folders/smb.html.md index 89546eda8..6b88857e4 100644 --- a/website/source/docs/synced-folders/smb.html.md +++ b/website/source/docs/synced-folders/smb.html.md @@ -3,8 +3,8 @@ layout: "docs" page_title: "SMB - Synced Folders" sidebar_current: "syncedfolder-smb" description: |- - Vagrant can use SMB as a mechanism to create a bi-directional synced folder - between the host machine and the Vagrant machine. + Vagrant can use SMB as a mechanism to create a bi-directional synced folder + between the host machine and the Vagrant machine. --- # SMB @@ -19,9 +19,9 @@ SMB is built-in to Windows machines and provides a higher performance alternative to some other mechanisms such as VirtualBox shared folders.
- Windows only! SMB is currently only supported - when the host machine is Windows. The guest machine can be Windows - or Linux. + Windows only! SMB is currently only supported + when the host machine is Windows. The guest machine can be Windows + or Linux.
## Prerequisites diff --git a/website/source/docs/vagrantfile/version.html.md b/website/source/docs/vagrantfile/version.html.md index 5840a9942..21a189a9f 100644 --- a/website/source/docs/vagrantfile/version.html.md +++ b/website/source/docs/vagrantfile/version.html.md @@ -3,9 +3,9 @@ layout: "docs" page_title: "Configuration Version - Vagrantfile" sidebar_current: "vagrantfile-version" description: |- - Configuration versions are the mechanism by which Vagrant 1.1+ is able to - remain backwards compatible with Vagrant 1.0.x Vagrantfiles, while introducing - dramatically new features and configuration options. + Configuration versions are the mechanism by which Vagrant 1.1+ is able to + remain backwards compatible with Vagrant 1.0.x Vagrantfiles, while introducing + dramatically new features and configuration options. --- # Configuration Version @@ -57,8 +57,8 @@ end ```
- What is Vagrant::Config.run? - You may see this in Vagrantfiles. This was actually how Vagrant 1.0.x - did configuration. In Vagrant 1.1+, this is synonymous with - Vagrant.configure("1"). + What is Vagrant::Config.run? + You may see this in Vagrantfiles. This was actually how Vagrant 1.0.x + did configuration. In Vagrant 1.1+, this is synonymous with + Vagrant.configure("1").
diff --git a/website/source/docs/virtualbox/boxes.html.md b/website/source/docs/virtualbox/boxes.html.md index 2e1142dd2..e507152cb 100644 --- a/website/source/docs/virtualbox/boxes.html.md +++ b/website/source/docs/virtualbox/boxes.html.md @@ -3,8 +3,8 @@ layout: "docs" page_title: "Creating a Base Box - VirtualBox Provider" sidebar_current: "providers-virtualbox-boxes" description: |- - As with every Vagrant provider, the Vagrant VirtualBox provider has a custom - box format that affects how base boxes are made. + As with every Vagrant provider, the Vagrant VirtualBox provider has a custom + box format that affects how base boxes are made. --- # Creating a Base Box @@ -24,11 +24,11 @@ Additionally, it is helpful to understand the [basics of the box file format](/docs/boxes/format.html).
- Advanced topic! This is a reasonably advanced topic that - a beginning user of Vagrant does not need to understand. If you are - just getting started with Vagrant, skip this and use an available - box. If you are an experienced user of Vagrant and want to create - your own custom boxes, this is for you. + Advanced topic! This is a reasonably advanced topic that + a beginning user of Vagrant does not need to understand. If you are + just getting started with Vagrant, skip this and use an available + box. If you are an experienced user of Vagrant and want to create + your own custom boxes, this is for you.
## Virtual Machine diff --git a/website/source/docs/virtualbox/configuration.html.md b/website/source/docs/virtualbox/configuration.html.md index 104afda70..fe6040d59 100644 --- a/website/source/docs/virtualbox/configuration.html.md +++ b/website/source/docs/virtualbox/configuration.html.md @@ -71,9 +71,9 @@ If you do not want backward compatbility and want to force users to support linked cloning, you can use `Vagrant.require_version` with 1.8.
- Note: the generated master VMs are currently not removed - automatically by Vagrant. This has to be done manually. However, a master - VM can only be removed when there are no linked clones connected to it. + Note: the generated master VMs are currently not removed + automatically by Vagrant. This has to be done manually. However, a master + VM can only be removed when there are no linked clones connected to it.
## VBoxManage Customizations diff --git a/website/source/docs/vmware/boxes.html.md b/website/source/docs/vmware/boxes.html.md index 2b4739d07..5b7eb653a 100644 --- a/website/source/docs/vmware/boxes.html.md +++ b/website/source/docs/vmware/boxes.html.md @@ -3,8 +3,8 @@ layout: "docs" page_title: "Box Format - VMware Provider" sidebar_current: "providers-vmware-boxes" description: |- - As with every Vagrant provider, the Vagrant VMware providers have a custom box - format. + As with every Vagrant provider, the Vagrant VMware providers have a custom box + format. --- # Boxes @@ -18,11 +18,11 @@ of Vagrant will provide additional mechanisms for automatically creating such images.
- Note: This is a reasonably advanced topic that - a beginning user of Vagrant does not need to understand. If you are - just getting started with Vagrant, skip this and use an available - box. If you are an experienced user of Vagrant and want to create - your own custom boxes, this is for you. + Note: This is a reasonably advanced topic that + a beginning user of Vagrant does not need to understand. If you are + just getting started with Vagrant, skip this and use an available + box. If you are an experienced user of Vagrant and want to create + your own custom boxes, this is for you.
Prior to reading this page, please understand the @@ -62,9 +62,9 @@ in the box into a privately managed "vmwarevm" folder, and uses the first "vmx" file found to control the machine.
- Vagrant 1.8 and higher support linked clones. Prior versions - of Vagrant do not support linked clones. For more information on - linked clones, please see the documentation. + Vagrant 1.8 and higher support linked clones. Prior versions + of Vagrant do not support linked clones. For more information on + linked clones, please see the documentation.
## Installed Software diff --git a/website/source/docs/vmware/usage.html.md b/website/source/docs/vmware/usage.html.md index d317322cc..82d7414a5 100644 --- a/website/source/docs/vmware/usage.html.md +++ b/website/source/docs/vmware/usage.html.md @@ -44,8 +44,8 @@ This will download and bring up a new VMware Fusion/Workstation virtual machine in Vagrant.
- Note: At some point in the future, the providers - will probably be merged into a single `vagrant-vmware` plugin. For now, - the Workstation and Fusion codebases are different enough that they - are separate plugins. + Note: At some point in the future, the providers + will probably be merged into a single `vagrant-vmware` plugin. For now, + the Workstation and Fusion codebases are different enough that they + are separate plugins.
diff --git a/website/source/index.html.erb b/website/source/index.html.erb index a03de9591..191957092 100644 --- a/website/source/index.html.erb +++ b/website/source/index.html.erb @@ -1,113 +1,113 @@ --- description: |- - Vagrant enables users to create and configure lightweight, reproducible, and - portable development environments. + Vagrant enables users to create and configure lightweight, reproducible, and + portable development environments. ---
-
-
-
+
+
+
-
-
-
-

Development
environments
made easy.

-

Create and configure lightweight, reproducible, and portable development environments.

-
-
-
+
+
+
+

Development
environments
made easy.

+

Create and configure lightweight, reproducible, and portable development environments.

+
+
+
-
- -
- Download -
- +
+ +
+ Download +
+ - -
- Get Started -
- -
-
-
-
+ +
+ Get Started +
+ +
+
+
+ -
-
-
-

- Vagrant will change how you work -

-
-
-
+
+
+
+

+ Vagrant will change how you work +

+
+
+
-
-

Set Up

-

- Download and install Vagrant within minutes on Mac OS X, Windows, or a popular distribution of Linux. No complicated setup process, just a simple to use OS-standard installer. -

-
+
+

Set Up

+

+ Download and install Vagrant within minutes on Mac OS X, Windows, or a popular distribution of Linux. No complicated setup process, just a simple to use OS-standard installer. +

+
-
-

Configure

-

- Create a single file for your project to describe the type of machine you want, the software that needs to be installed, and the way you want to access the machine. Store this file with your project code. -

-
+
+

Configure

+

+ Create a single file for your project to describe the type of machine you want, the software that needs to be installed, and the way you want to access the machine. Store this file with your project code. +

+
-
-

Work

-

- Run a single command — "vagrant up" — and sit back as Vagrant puts together your complete development environment. Say goodbye to the "works on my machine" excuse as Vagrant creates identical development environments for everyone on your team. -

-
-
-
-
-
+
+

Work

+

+ Run a single command — "vagrant up" — and sit back as Vagrant puts together your complete development environment. Say goodbye to the "works on my machine" excuse as Vagrant creates identical development environments for everyone on your team. +

+
+
+
+
+
-
-
-
-
+
+
+
+
-

- See how easy it is -

- 
+          

+            See how easy it is
+          

+          
 $ vagrant init hashicorp/precise64
 $ vagrant up
-					

-
-
-
- -
- get started» -
- -
-
-
+ +
+
+
+ +
+ get started» +
+ +
+
+
-
-
-
-
-

- Trusted by -

-
- <%= image_tag "customers.png", alt: "customers", width: 941, height: 111 %> -
-
-
-
-
+
+
+
+
+

+ Trusted by +

+
+ <%= image_tag "customers.png", alt: "customers", width: 941, height: 111 %> +
+
+
+
+
-
+ diff --git a/website/source/layouts/_footer.erb b/website/source/layouts/_footer.erb index 4c1758ab6..0ea9ac0ed 100644 --- a/website/source/layouts/_footer.erb +++ b/website/source/layouts/_footer.erb @@ -66,7 +66,7 @@ window.onload = function(){ diff --git a/website/source/layouts/_header.erb b/website/source/layouts/_header.erb index c576312d8..84d5e9a27 100644 --- a/website/source/layouts/_header.erb +++ b/website/source/layouts/_header.erb @@ -19,48 +19,48 @@ "> - + <%= yield_content :head %>
"> -
-
-
-
-
- - by<%= partial "layouts/svg/svg-by-hashicorp" %><%= partial "layouts/svg/svg-hashicorp-logo" %>Hashicorp -
- -
- +
+
+
diff --git a/website/source/layouts/about.erb b/website/source/layouts/about.erb index 925397634..9ee1e5011 100644 --- a/website/source/layouts/about.erb +++ b/website/source/layouts/about.erb @@ -1,22 +1,22 @@ <% wrap_layout :inner do %> - <% content_for :sidebar do %> - + <% end %> - <%= yield %> + <%= yield %> <% end %> diff --git a/website/source/layouts/docs.erb b/website/source/layouts/docs.erb index bb2ff4a6c..4933ea503 100644 --- a/website/source/layouts/docs.erb +++ b/website/source/layouts/docs.erb @@ -1,238 +1,238 @@ <% wrap_layout :inner do %> - <% content_for :sidebar do %> - + <% end %> - <%= yield %> + <%= yield %> <% end %> diff --git a/website/source/layouts/downloads.erb b/website/source/layouts/downloads.erb index 352e9b8e5..4f2a35771 100644 --- a/website/source/layouts/downloads.erb +++ b/website/source/layouts/downloads.erb @@ -1,16 +1,16 @@ <% wrap_layout :inner do %> - <% content_for :sidebar do %> - + <% end %> - <%= yield %> + <%= yield %> <% end %> diff --git a/website/source/layouts/inner.erb b/website/source/layouts/inner.erb index 602fdcac7..e77df4ea1 100644 --- a/website/source/layouts/inner.erb +++ b/website/source/layouts/inner.erb @@ -1,13 +1,13 @@ <% wrap_layout :layout do %>
- + -
-
- <%= yield %> -
-
+
+
+ <%= yield %> +
+
<% end %> diff --git a/website/source/layouts/vmware.erb b/website/source/layouts/vmware.erb index 8a72fb1be..dc9a12480 100644 --- a/website/source/layouts/vmware.erb +++ b/website/source/layouts/vmware.erb @@ -1,22 +1,22 @@ <% wrap_layout :inner do %> - <% content_for :sidebar do %> - + <% end %> - <%= yield %> + <%= yield %> <% end %> diff --git a/website/source/sponsors.html.erb b/website/source/sponsors.html.erb index aa019a093..1e6b16b7b 100644 --- a/website/source/sponsors.html.erb +++ b/website/source/sponsors.html.erb @@ -3,10 +3,10 @@ layout: "about" sidebar_current: "about-sponsors" page_title: "Sponsors" description: |- - The companies on this page special recognition for their contributions - to Vagrant. These companies consistently provide resources which help the - project run smoothly by supporting hosting costs, providing testing machines, - donating their services, etc. + The companies on this page special recognition for their contributions + to Vagrant. These companies consistently provide resources which help the + project run smoothly by supporting hosting costs, providing testing machines, + donating their services, etc. ---

Sponsors

@@ -19,10 +19,10 @@ donating their services, etc.

- +
diff --git a/website/source/vmware/index.html.erb b/website/source/vmware/index.html.erb index e6c264255..225c73c12 100644 --- a/website/source/vmware/index.html.erb +++ b/website/source/vmware/index.html.erb @@ -1,399 +1,399 @@ --- page_title: "VMware Integration" description: |- - The Vagrant VMware plugin provides rock-solid stability, improved performance, - and dedicated support for using VMware and Vagrant. + The Vagrant VMware plugin provides rock-solid stability, improved performance, + and dedicated support for using VMware and Vagrant. ---
-
-
-
+
+
+
-
-
-
-

Supercharged Vagrant environments

-

- Use Vagrant with VMware Fusion or Workstation for improved - stability, performance, and support. -

-
-
-
+
+
+
+

Supercharged Vagrant environments

+

+ Use Vagrant with VMware Fusion or Workstation for improved + stability, performance, and support. +

+
+
+
-
- -
- learn more -
- +
+ +
+ learn more +
+ - -
- buy now -
- -
-
-
-
+ +
+ buy now +
+ +
+
+
+ - -
-
-
-

- VMware Makes Your Life Better -

-
+ +
+
+
+

+ VMware Makes Your Life Better +

+
-
-
-
-

Same Vagrant Workflow

+
+
+
+

Same Vagrant Workflow

-

- "vagrant up," "vagrant ssh," "vagrant destroy." The same Vagrant - workflow you know and love. Vastly improve your work environments - without having to re-educate your team. -

-
+

+ "vagrant up," "vagrant ssh," "vagrant destroy." The same Vagrant + workflow you know and love. Vastly improve your work environments + without having to re-educate your team. +

+
-
-

Unparalleled Performance

+
+

Unparalleled Performance

-

- VMware screams, with industry-leading performance1 - based on the same hypervisor technology in use by 98% of the Fortune 500. - Get all the performance gains paired with the ease of use of Vagrant. -

-
-
+

+ VMware screams, with industry-leading performance1 + based on the same hypervisor technology in use by 98% of the Fortune 500. + Get all the performance gains paired with the ease of use of Vagrant. +

+
+
-
-
-

Rock Solid Stability

+
+
+

Rock Solid Stability

-

- The VMware hypervisor has been in production use since 1999. - All their products share the same, robust core that powers - the world's largest organizations. With the VMware provider, Vagrant - now runs on the strength of the same foundation. -

-
+

+ The VMware hypervisor has been in production use since 1999. + All their products share the same, robust core that powers + the world's largest organizations. With the VMware provider, Vagrant + now runs on the strength of the same foundation. +

+
-
-

Uncompromised Portability

+
+

Uncompromised Portability

-

- VMware virtual machines run on Mac OS X, Windows, and Linux. - Vagrant provides support for both VMware Fusion (Mac OS X) and - VMware Workstation (Linux and Windows), which are able to run - the same virtual machines across multiple platforms. -

-
-
+

+ VMware virtual machines run on Mac OS X, Windows, and Linux. + Vagrant provides support for both VMware Fusion (Mac OS X) and + VMware Workstation (Linux and Windows), which are able to run + the same virtual machines across multiple platforms. +

+
+
-
-
-

Professional Support

+
+
+

Professional Support

-

- Every purchase of the Vagrant VMware provider comes with - direct email support. VMware products themselves are eligible for - professional support from VMware. Someone always has your back - in case things are not working as well as they should be. -

-
+

+ Every purchase of the Vagrant VMware provider comes with + direct email support. VMware products themselves are eligible for + professional support from VMware. Someone always has your back + in case things are not working as well as they should be. +

+
-
-

♥ Open Source

+
+

♥ Open Source

-

- Vagrant is free and open source. While the VMware providers - are not, the revenue is used to continue to develop, support, - and grow Vagrant and the community around it. -

-
-
+

+ Vagrant is free and open source. While the VMware providers + are not, the revenue is used to continue to develop, support, + and grow Vagrant and the community around it. +

+
+
-
-
-

- 1According to this article in MacWorld vs. Parallels Desktop 7 -

-
-
-
-
-
+
+
+

+ 1According to this article in MacWorld vs. Parallels Desktop 7 +

+
+
+
+ +
- -
-
-
-
+ +
+
+
+
-

- Pricing & Purchase -

-
-
-
-
-
-

- Price: $79 per seat. -

-

- A single seat can be used on two computers (such as a desktop - and a laptop) for a single person. The license is valid forever - with access to free maintenance updates. Future major updates may require - an upgrade fee. -

-

- Choose the provider you want below and enter the number of seats - you wish to purchase. Then, click the buy button and complete the - flow and instructions to install and download the software will - be emailed to you. -

-
-
- - -
-
- - -
-
+

+ Pricing & Purchase +

+
+
+
+
+
+

+ Price: $79 per seat. +

+

+ A single seat can be used on two computers (such as a desktop + and a laptop) for a single person. The license is valid forever + with access to free maintenance updates. Future major updates may require + an upgrade fee. +

+

+ Choose the provider you want below and enter the number of seats + you wish to purchase. Then, click the buy button and complete the + flow and instructions to install and download the software will + be emailed to you. +

+
+
+ + +
+
+ + +
+
-
- The provider license does not include a license to the VMware - software, which must be purchased separately. If you are buying over 150 licenses, contact sales@hashicorp.com for volume pricing. -
-
- Previous plugin versions may not support the latest VMware products. Please visit the license upgrade center to check if your license requires an upgrade before you upgrade your VMware products. -
-
- For reseller information, click here. -
-
-
-
-
-
+
+ The provider license does not include a license to the VMware + software, which must be purchased separately. If you are buying over 150 licenses, contact sales@hashicorp.com for volume pricing. +
+
+ Previous plugin versions may not support the latest VMware products. Please visit the license upgrade center to check if your license requires an upgrade before you upgrade your VMware products. +
+
+ For reseller information, click here. +
+
+
+
+ +
- -
-
-
-
-

- Frequently Asked Questions -

-
-
+ +
+
+
+
+

+ Frequently Asked Questions +

+
+
-
-
-

Do you offer a trial for the Vagrant VMware plugins?

-

- We do not offer a trial mechanism at this time, but we do offer a - 30-day, no questions asked, 100% money-back guarantee. If you are - not satisfied with the product, contact us within 30 days and you - will receive a full refund. -

-
-
+
+
+

Do you offer a trial for the Vagrant VMware plugins?

+

+ We do not offer a trial mechanism at this time, but we do offer a + 30-day, no questions asked, 100% money-back guarantee. If you are + not satisfied with the product, contact us within 30 days and you + will receive a full refund. +

+
+
-
-
-

Do you offer educational discounts on the Vagrant VMware plugins?

-

- We offer an academic discount of 10% for the Vagrant VMware plugins. - However, we require proof that you are a current student or employee - in academia. Please contact support with any one of - the following forms of proof: +

+
+

Do you offer educational discounts on the Vagrant VMware plugins?

+

+ We offer an academic discount of 10% for the Vagrant VMware plugins. + However, we require proof that you are a current student or employee + in academia. Please contact support with any one of + the following forms of proof: -

    -

  • A picture of your current university ID

    • -

  • An email from your official .edu school email address

    • -

  • A copy of something on university letterhead indicating you are currently enrolled as a student

    • -
-

-
-
+
    +

  • A picture of your current university ID

    • +

  • An email from your official .edu school email address

    • +

  • A copy of something on university letterhead indicating you are currently enrolled as a student

    • +
+

+
+
-
-
-

I already own a license, am I eligible for an upgrade?

-

- Existing license holders may check their upgrade eligibility by - visiting the license upgrade center. - If you are eligible for an upgrade, the system will generate a - unique discount code that may be used when purchasing the new - license. -

-
-
+
+
+

I already own a license, am I eligible for an upgrade?

+

+ Existing license holders may check their upgrade eligibility by + visiting the license upgrade center. + If you are eligible for an upgrade, the system will generate a + unique discount code that may be used when purchasing the new + license. +

+
+
-
-
-

Do I need to pay for upgrades to my license?

-

- The Vagrant VMware plugin licenses are valid for specific VMware - product versions at the time of purchase. When new versions of - VMware products are released, significant changes to the plugin code - are often required to support this new version. For this reason, you - may need to upgrade your current license to work with the new - version of the VMware product. Customers can check their license - upgrade eligibility by visiting the - License Upgrade Center - and entering the email address with which they made the original - purchase. -

-

- Please note: your existing license will continue to work with all - previous versions of the VMware products. If you do not wish to - update at this time, you can rollback your VMware installation to an - older version. -

-
-
+
+
+

Do I need to pay for upgrades to my license?

+

+ The Vagrant VMware plugin licenses are valid for specific VMware + product versions at the time of purchase. When new versions of + VMware products are released, significant changes to the plugin code + are often required to support this new version. For this reason, you + may need to upgrade your current license to work with the new + version of the VMware product. Customers can check their license + upgrade eligibility by visiting the + License Upgrade Center + and entering the email address with which they made the original + purchase. +

+

+ Please note: your existing license will continue to work with all + previous versions of the VMware products. If you do not wish to + update at this time, you can rollback your VMware installation to an + older version. +

+
+
-
-
-

Where can I find the EULA for the Vagrant VMware Plugins?

-

- The EULA for the Vagrant VMware plugins - is available on the Vagrant website. -

-
-
+
+
+

Where can I find the EULA for the Vagrant VMware Plugins?

+

+ The EULA for the Vagrant VMware plugins + is available on the Vagrant website. +

+
+
-
-
-

Do you offer incentives for resellers?

-

- All our reseller information can be found on the - Reseller Information page. -

-
-
+
+
+

Do you offer incentives for resellers?

+

+ All our reseller information can be found on the + Reseller Information page. +

+
+
-
-
-

Do you offer bulk/volume discounts for the Vagrant VMware plugins?

-

- We certainly do! Email support - with the number of licenses you need and we can give you bulk pricing - information. Please note that bulk pricing requires the purchase of - at least 150 seats. -

-
-
+
+
+

Do you offer bulk/volume discounts for the Vagrant VMware plugins?

+

+ We certainly do! Email support + with the number of licenses you need and we can give you bulk pricing + information. Please note that bulk pricing requires the purchase of + at least 150 seats. +

+
+
-
-
-

Since each license comes with two "seats", can I use one seat for the Vagrant VMware Fusion plugin and one seat for the Vagrant VMware Workstation plugin?

-

- Unfortunately this is not possible at this time. The Vagrant VMware - Fusion plugin and the Vagrant VMware Workstation plugin are separate - products and cannot be shared in this manner. We apologize for the - inconvenience. -

-

- We do offer a 50% discount off the purchase of the other Vagrant - plugin for individual users and qualified candidates. Certain - restrictions do apply. Please email support - to find out if you qualify. Unfortunately we cannot retroactively - apply this discount, so please email support before making your - purchase. -

-
-
+
+
+

Since each license comes with two "seats", can I use one seat for the Vagrant VMware Fusion plugin and one seat for the Vagrant VMware Workstation plugin?

+

+ Unfortunately this is not possible at this time. The Vagrant VMware + Fusion plugin and the Vagrant VMware Workstation plugin are separate + products and cannot be shared in this manner. We apologize for the + inconvenience. +

+

+ We do offer a 50% discount off the purchase of the other Vagrant + plugin for individual users and qualified candidates. Certain + restrictions do apply. Please email support + to find out if you qualify. Unfortunately we cannot retroactively + apply this discount, so please email support before making your + purchase. +

+
+
-
-
-

I accidentally bought the wrong Vagrant VMware plugin, can I switch?

-

- Sure! Even though the Vagrant VMware Fusion plugin and the Vagrant - VMware Workstation plugin are different products, they are the same - price and fall under the same EULA. As such, we can transfer the - license for you. Please contact support - for assistance. Be sure to include your original order number. You - may be asked to confirm details your purchase to verify the - authenticity of your request. -

-
-
+
+
+

I accidentally bought the wrong Vagrant VMware plugin, can I switch?

+

+ Sure! Even though the Vagrant VMware Fusion plugin and the Vagrant + VMware Workstation plugin are different products, they are the same + price and fall under the same EULA. As such, we can transfer the + license for you. Please contact support + for assistance. Be sure to include your original order number. You + may be asked to confirm details your purchase to verify the + authenticity of your request. +

+
+
-
-
-

Does this include the VMware software?

-

- The Vagrant VMware Plugin requires the separate purchase of VMware - Fusion/Workstation from VMware. The VMware product is not bundled - with the plugin. -

-
-
+
+
+

Does this include the VMware software?

+

+ The Vagrant VMware Plugin requires the separate purchase of VMware + Fusion/Workstation from VMware. The VMware product is not bundled + with the plugin. +

+
+
-
-
-

Why is the Vagrant VMware plugin not working with my trial version of VMware Fusion/Workstation?

-

- While we have not been able to isolate to a specific issue or cause, - the Vagrant VMware Fusion and Vagrant VMware Workstation plugins are - sometimes incompatible with the trial versions of the VMware - products. -

-

- Please try restarting your computer and running the VMware software - manually. Occassionally you must accept the license agreement before - VMware will run. If you do not see any errors when opening the - VMware GUI, you may need to purchase the full version to use the - plugin. We apologize for the inconvenience. -

-
-
+
+
+

Why is the Vagrant VMware plugin not working with my trial version of VMware Fusion/Workstation?

+

+ While we have not been able to isolate to a specific issue or cause, + the Vagrant VMware Fusion and Vagrant VMware Workstation plugins are + sometimes incompatible with the trial versions of the VMware + products. +

+

+ Please try restarting your computer and running the VMware software + manually. Occassionally you must accept the license agreement before + VMware will run. If you do not see any errors when opening the + VMware GUI, you may need to purchase the full version to use the + plugin. We apologize for the inconvenience. +

+
+
-
-
-

Can I use VMware Workstation Player?

-

- Some features of the Vagrant VMware Workstation plugin will - work with VMware Player, but it is not officially supported. -

-
-
+
+
+

Can I use VMware Workstation Player?

+

+ Some features of the Vagrant VMware Workstation plugin will + work with VMware Player, but it is not officially supported. +

+
+
-
-
-

Do I need VMware Fusion/Workstation Pro or just the regular version?

-

- The Vagrant VMware plugin is compatible with both the regular and - Pro versions of VMware Fusion and VMware Workstation. However, some - advanced features (such as linked clones), are only supported by the - Pro versions of the VMware software. -

-

- Please consult the VMware documentation to determine which features - are supported by the Pro and non-Pro versions to determine which - product you need to purchase. -

-
-
-
-
+
+
+

Do I need VMware Fusion/Workstation Pro or just the regular version?

+

+ The Vagrant VMware plugin is compatible with both the regular and + Pro versions of VMware Fusion and VMware Workstation. However, some + advanced features (such as linked clones), are only supported by the + Pro versions of the VMware software. +

+

+ Please consult the VMware documentation to determine which features + are supported by the Pro and non-Pro versions to determine which + product you need to purchase. +

+
+
+
+
- + diff --git a/website/source/vmware/privacy-policy.html.md b/website/source/vmware/privacy-policy.html.md index 05df65d0f..c32955c62 100644 --- a/website/source/vmware/privacy-policy.html.md +++ b/website/source/vmware/privacy-policy.html.md @@ -29,9 +29,9 @@ If you have provided us with a means of contacting you, we may use such means to B. Information Collected Automatically: -• Whenever you interact with our Services, we automatically receive and record information on our server logs from your browser including your IP address, "cookie" information, and the page you requested. "Cookies" are identifiers we transfer to your computer or mobile device that allow us to recognize your browser or mobile device and tell us how and when pages and features in our Services are visited and by how many people. You may be able to change the preferences on your browser or mobile device to prevent or limit your computer or device's acceptance of cookies, but this may prevent you from taking advantage of some of our features. Our advertising partners may also transmit cookies to your computer or device, when you click on ads that appear on the Services. Also, if you click on a link to a third party website, such third party may also transmit cookies to you. This Privacy Policy does not cover the use of cookies by any third parties. +• Whenever you interact with our Services, we automatically receive and record information on our server logs from your browser including your IP address, "cookie" information, and the page you requested. "Cookies" are identifiers we transfer to your computer or mobile device that allow us to recognize your browser or mobile device and tell us how and when pages and features in our Services are visited and by how many people. You may be able to change the preferences on your browser or mobile device to prevent or limit your computer or device's acceptance of cookies, but this may prevent you from taking advantage of some of our features. Our advertising partners may also transmit cookies to your computer or device, when you click on ads that appear on the Services. Also, if you click on a link to a third party website, such third party may also transmit cookies to you. This Privacy Policy does not cover the use of cookies by any third parties. -• When we collect usage information (such as the numbers and frequency of visitors to the Website), we only use this data in aggregate form, and not in a manner that would identify you personally. For example, this aggregate data tells us how often users use parts of the Services, so that we can make the Services appealing to as many users as possible. We may also provide this aggregate information to our partners; our partners may use such information to understand how often and in what ways people use our Services, so that they, too, can provide you with an optimal experience. We never disclose aggregate information to a partner in a manner that would identify you personally. +• When we collect usage information (such as the numbers and frequency of visitors to the Website), we only use this data in aggregate form, and not in a manner that would identify you personally. For example, this aggregate data tells us how often users use parts of the Services, so that we can make the Services appealing to as many users as possible. We may also provide this aggregate information to our partners; our partners may use such information to understand how often and in what ways people use our Services, so that they, too, can provide you with an optimal experience. We never disclose aggregate information to a partner in a manner that would identify you personally. III. WILL COMPANY SHARE ANY OF THE PERSONAL INFORMATION IT RECEIVES? @@ -64,8 +64,8 @@ The information you can view, update, and delete may change as the Services chan VI. WHAT CHOICES DO I HAVE? -• You can always opt not to disclose information to use, but keep in mind some information may be needed to register with us or to take advantage of some of our special features. -• You may be able to add, update, or delete information as explained in Section V above. When you update information, however, we may maintain a copy of the unrevised information in our records. You may request deletion of your account by emailing support@hashicorp.com. Please note that some information may remain in our records after your deletion of such information from your account. We may use any aggregated data derived from or incorporating your Personal Information after you update or delete it, but not in a manner that would identify you personally. +• You can always opt not to disclose information to use, but keep in mind some information may be needed to register with us or to take advantage of some of our special features. +• You may be able to add, update, or delete information as explained in Section V above. When you update information, however, we may maintain a copy of the unrevised information in our records. You may request deletion of your account by emailing support@hashicorp.com. Please note that some information may remain in our records after your deletion of such information from your account. We may use any aggregated data derived from or incorporating your Personal Information after you update or delete it, but not in a manner that would identify you personally. VII. CHANGES TO THIS PRIVACY POLICY We may amend this Privacy Policy from time to time. Use of information we collect now is subject to the Privacy Policy in effect at the time such information is used. If we make changes in the way we use Personal Information, we will notify you by posting an announcement on our Website or sending you a message. You are bound by any changes to the Privacy Policy when you use the Services after such changes have been first posted.