Use SSL and HTTPS links where appropriate

This commit is contained in:
Seth Vargo 2016-01-25 13:14:54 -05:00
parent 1ae499670e
commit 1166800b65
16 changed files with 24 additions and 24 deletions

View File

@ -2851,7 +2851,7 @@ compatibility.
in a saved state. [GH-123]
- Added `config.chef.recipe_url` which allows you to specify a URL to
a gzipped tar file for chef solo to download cookbooks. See the
[chef-solo docs](http://wiki.opscode.com/display/chef/Chef+Solo#ChefSolo-RunningfromaURL) for more information.
[chef-solo docs](https://docs.chef.io/chef_solo.html) for more information.
[GH-121]
- Added `vagrant box repackage` which repackages boxes which have
been added. This is useful in case you want to redistribute a base

View File

@ -37,5 +37,5 @@ The following guidelines for contribution should be followed if you want to subm
# Additional Resources
* [General GitHub documentation](http://help.github.com/)
* [GitHub pull request documentation](http://help.github.com/send-pull-requests/)
* [General GitHub documentation](https://help.github.com/)
* [GitHub pull request documentation](https://help.github.com/send-pull-requests/)

View File

@ -3,7 +3,7 @@
* Website: [https://www.vagrantup.com/](https://www.vagrantup.com/)
* Source: [https://github.com/mitchellh/vagrant](https://github.com/mitchellh/vagrant)
* IRC: `#vagrant` on Freenode
* Mailing list: [Google Groups](http://groups.google.com/group/vagrant-up)
* Mailing list: [Google Groups](https://groups.google.com/group/vagrant-up)
Vagrant is a tool for building and distributing development environments.
@ -21,12 +21,12 @@ between Windows, Mac OS X, and Linux.
For the quick-start, we'll bring up a development machine on
[VirtualBox](https://www.virtualbox.org/) because it is free and works
on all major platforms. Vagrant can, however, work with almost any
system such as [OpenStack] (https://www.openstack.org/), [VMware] (http://www.vmware.com/), [Docker] (https://docs.docker.com/), etc.
system such as [OpenStack] (https://www.openstack.org/), [VMware] (https://www.vmware.com/), [Docker] (https://docs.docker.com/), etc.
First, make sure your development machine has
[VirtualBox](https://www.virtualbox.org/)
installed. After this,
[download and install the appropriate Vagrant package for your OS](http://www.vagrantup.com/downloads).
[download and install the appropriate Vagrant package for your OS](https://www.vagrantup.com/downloads.html).
To build your first virtual environment:
@ -40,7 +40,7 @@ the box doesn't already exist on your system.
## Getting Started Guide
To learn how to build a fully functional development environment, follow the
[getting started guide](http://docs.vagrantup.com/v2/getting-started/index.html).
[getting started guide](https://www.vagrantup.com/docs/getting-started/index.html).
## Installing the Gem from Git

View File

@ -1,7 +1,7 @@
# Insecure Keypair
These keys are the "insecure" public/private keypair we offer to
[base box creators](http://docs.vagrantup.com/v2/boxes/base.html) for use in their base boxes so that
[base box creators](https://www.vagrantup.com/docs/boxes/base.html) for use in their base boxes so that
vagrant installations can automatically SSH into the boxes.
If you're working with a team or company or with a custom box and

View File

@ -212,7 +212,7 @@ module Vagrant
end
def clear_line
# See: http://en.wikipedia.org/wiki/ANSI_escape_code
# See: https://en.wikipedia.org/wiki/ANSI_escape_code
reset = "\r\033[K"
info(reset, new_line: false)

View File

@ -48,7 +48,7 @@ module Vagrant
# Verify that we have administrative privileges. The odd method of
# detecting this is based on this StackOverflow question:
#
# http://stackoverflow.com/questions/560366/
# https://stackoverflow.com/questions/560366/
# detect-if-running-with-administrator-privileges-under-windows-xp
begin
Win32::Registry::HKEY_USERS.open("S-1-5-19") {}

View File

@ -5,7 +5,7 @@ module VagrantPlugins
def build_install_opts(o, options)
options[:plugin_sources] = [
"https://rubygems.org",
"http://gems.hashicorp.com",
"https://gems.hashicorp.com",
]
o.on("--entry-point NAME", String,

View File

@ -43,7 +43,7 @@ module VagrantPlugins
# Clear the sources so that installation uses custom sources
old_sources = Gem.sources
Gem.sources = Gem.default_sources
Gem.sources << "http://gems.hashicorp.com"
Gem.sources << "https://gems.hashicorp.com"
# Use a silent UI so that we have no output
Gem::DefaultUserInteraction.use_ui(Gem::SilentUI.new) do

View File

@ -92,7 +92,7 @@ module VagrantPlugins
@logger.debug("querying network adapters")
# Get all NICs that have a MAC address
# http://msdn.microsoft.com/en-us/library/windows/desktop/aa394216(v=vs.85).aspx
# https://msdn.microsoft.com/en-us/library/windows/desktop/aa394216(v=vs.85).aspx
adapters = @communicator.execute(WQL_NET_ADAPTERS_V2, { shell: :wql } )[:win32_network_adapter]
@logger.debug("#{adapters.inspect}")
return adapters

View File

@ -12,7 +12,7 @@ en:
The Git binary '%{bin}' could not be found. Please ensure you
have downloaded and installed the latest version of Git:
http://git-scm.com/downloads
https://git-scm.com/downloads
missing_attribute: |-
Missing required attribute '%{attribute}'. The Vagrant Heroku Push
plugin requires you set this attribute. Please set this attribute in

View File

@ -271,13 +271,13 @@ en:
You're running an up-to-date version of Vagrant!
version_no_checkpoint: |-
Vagrant was unable to check for the latest version of Vagrant.
Please check manually at http://www.vagrantup.com
Please check manually at http:s//www.vagrantup.com
version_upgrade_howto: |-
To upgrade to the latest version, visit the downloads page and
download and install the latest version of Vagrant from the URL
below:
http://www.vagrantup.com/downloads.html
https://www.vagrantup.com/downloads.html
If you're curious what changed in the latest release, view the
CHANGELOG below:
@ -500,7 +500,7 @@ en:
notify the box creator that the box is corrupt. Documentation for
box file format can be found at the URL below:
http://docs.vagrantup.com/v2/boxes/format.html
https://www.vagrantup.com/docs/boxes/format.html
box_metadata_malformed: |-
The metadata for the box was malformed. The exact error
is shown below. Please contact the maintainer of the box so

View File

@ -7,7 +7,7 @@ Gem::Specification.new do |s|
s.platform = Gem::Platform::RUBY
s.authors = ["Mitchell Hashimoto", "John Bender"]
s.email = ["mitchell.hashimoto@gmail.com", "john.m.bender@gmail.com"]
s.homepage = "http://vagrantup.com"
s.homepage = "https://www.vagrantup.com"
s.license = 'MIT'
s.summary = "Build and distribute virtualized development environments."
s.description = "Vagrant is a tool for building and distributing virtualized development environments."

View File

@ -2,9 +2,9 @@
This is the repository for the [Vagrant website](https://www.vagrantup.com).
This is a [Middleman](http://middlemanapp.com) project, which builds a static
site from these source files. The site is hosted on [Heroku](http://heroku.com)
and then fronted by [Fastly](https://www.fastly.com).
This is a [Middleman](https://middlemanapp.com) project, which builds a static
site from these source files. The site is hosted fronted by
[Fastly](https://www.fastly.com).
## Contributions Welcome!

View File

@ -26,7 +26,7 @@ upgrades and use a stable API.
comfortable with Ruby should approach.
</div>
Plugins are written using [Ruby](http://www.ruby-lang.org/en/) and are packaged
Plugins are written using [Ruby](https://www.ruby-lang.org/en/) and are packaged
using [RubyGems](https://rubygems.org/). Familiarity with Ruby is required,
but the [packaging and distribution](/docs/plugins/packaging.html) section should help
guide you to packaging your plugin into a RubyGem.

View File

@ -181,7 +181,7 @@ root if a relative path is given.
## Custom Facts
Custom facts to be exposed by [Facter](http://puppetlabs.com/puppet/related-projects/facter/)
Custom facts to be exposed by [Facter](https://puppetlabs.com/facter)
can be specified as well:
```ruby

View File

@ -90,7 +90,7 @@ 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](http://license.hashicorp.com/upgrade/vmware2015)
license upgrade eligibility by visiting the [License Upgrade Center](https://license.hashicorp.com/upgrade/vmware2015)
and entering the email address with which they made the original purchase.
Your existing license will continue to work with all previous versions of the