Skip to content

Commit cba0277

Browse files
jescalanjescalan
committed
remove internal '.html' extensions
1 parent 23f4fc9 commit cba0277

File tree

101 files changed

+213
-213
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

101 files changed

+213
-213
lines changed

‎README.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
# Vagrant
22

3-
* Website: [https://www.vagrantup.com/](https://www.vagrantup.com/)
4-
* Source: [https://github.com/hashicorp/vagrant](https://github.com/hashicorp/vagrant)
5-
* HashiCorp Discuss: [https://discuss.hashicorp.com/c/vagrant/24](https://discuss.hashicorp.com/c/vagrant/24)
3+
- Website: [https://www.vagrantup.com/](https://www.vagrantup.com/)
4+
- Source: [https://github.com/hashicorp/vagrant](https://github.com/hashicorp/vagrant)
5+
- HashiCorp Discuss: [https://discuss.hashicorp.com/c/vagrant/24](https://discuss.hashicorp.com/c/vagrant/24)
66

77
Vagrant is a tool for building and distributing development environments.
88

@@ -41,12 +41,12 @@ the box doesn't already exist on your system.
4141
## Getting Started Guide
4242

4343
To learn how to build a fully functional development environment, follow the
44-
[getting started guide](https://www.vagrantup.com/docs/getting-started/index.html).
44+
[getting started guide](https://www.vagrantup.com/docs/getting-started).
4545

4646
## Installing from Source
4747

4848
If you want the bleeding edge version of Vagrant, we try to keep master pretty stable
49-
and you're welcome to give it a shot. Please review the installation page [here](https://www.vagrantup.com/docs/installation/source.html).
49+
and you're welcome to give it a shot. Please review the installation page [here](https://www.vagrantup.com/docs/installation/source).
5050

5151
## Contributing to Vagrant
5252

‎website/pages/docs/boxes/base.mdx

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -60,16 +60,16 @@ boxes.
6060

6161
Provider-specific guides for creating base boxes are linked below:
6262

63-
- [Docker Base Boxes](/docs/docker/boxes.html)
64-
- [Hyper-V Base Boxes](/docs/hyperv/boxes.html)
65-
- [VMware Base Boxes](/docs/vmware/boxes.html)
66-
- [VirtualBox Base Boxes](/docs/virtualbox/boxes.html)
63+
- [Docker Base Boxes](/docs/docker/boxes)
64+
- [Hyper-V Base Boxes](/docs/hyperv/boxes)
65+
- [VMware Base Boxes](/docs/vmware/boxes)
66+
- [VirtualBox Base Boxes](/docs/virtualbox/boxes)
6767

6868
### Packer and Vagrant Cloud
6969

7070
We strongly recommend using [Packer](https://www.packer.io) to create reproducible
7171
builds for your base boxes, as well as automating the builds. Read more about
72-
[automating Vagrant box creation with Packer](https://www.packer.io/guides/packer-on-cicd/build-image-in-cicd.html)
72+
[automating Vagrant box creation with Packer](https://www.packer.io/guides/packer-on-cicd/build-image-in-cicd)
7373
in the Packer documentation.
7474

7575
### Disk Space

‎website/pages/docs/boxes/format.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ description: |-
1212

1313
In the past, boxes were just [tar files](<https://en.wikipedia.org/wiki/Tar_(computing)>)
1414
of VirtualBox exports. With Vagrant supporting multiple
15-
[providers](/docs/providers/) and [versioning](/docs/boxes/versioning.html)
15+
[providers](/docs/providers/) and [versioning](/docs/boxes/versioning)
1616
now, box files are slightly more complicated.
1717

1818
Box files made for Vagrant 1.0.x (the VirtualBox export `tar` files) continue
@@ -37,7 +37,7 @@ Today, there are three different components:
3737

3838
- Box Information - This is a JSON document that can provide additional
3939
information about the box that displays when a user runs
40-
`vagrant box list -i`. More information is provided [here](/docs/boxes/info.html).
40+
`vagrant box list -i`. More information is provided [here](/docs/boxes/info).
4141

4242
The first two components are covered in more detail below.
4343

@@ -82,7 +82,7 @@ file.
8282
## Box Metadata
8383

8484
The metadata is an optional component for a box (but highly recommended)
85-
that enables [versioning](/docs/boxes/versioning.html), updating, multiple
85+
that enables [versioning](/docs/boxes/versioning), updating, multiple
8686
providers from a single file, and more.
8787

8888
-> **You do not need to manually make the metadata.** If you

‎website/pages/docs/boxes/index.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ anyone on any platform that Vagrant supports to bring up an identical
1616
working environment.
1717

1818
The `vagrant box` utility provides all the functionality for managing
19-
boxes. You can read the documentation on the [vagrant box](/docs/cli/box.html)
19+
boxes. You can read the documentation on the [vagrant box](/docs/cli/box)
2020
command for more information.
2121

2222
The easiest way to use a box is to add a box from the

‎website/pages/docs/boxes/info.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ hashicorp/bionic64 (virtualbox, 1.0.0)
2525
## Box Info
2626

2727
To accomplish this, you simply need to include a file named `info.json` when
28-
creating a [base box](/docs/boxes/base.html) which is a JSON document containing
28+
creating a [base box](/docs/boxes/base) which is a JSON document containing
2929
any and all relevant information that will be displayed to the user when the
3030
`-i` option is used with `vagrant box list`.
3131

@@ -39,5 +39,5 @@ any and all relevant information that will be displayed to the user when the
3939
There are no special keys or values in `info.json`, and Vagrant will print each
4040
key and value on its own line.
4141

42-
The [Box File Format](/docs/boxes/format.html) provides more information about what
42+
The [Box File Format](/docs/boxes/format) provides more information about what
4343
else goes into a Vagrant box.

‎website/pages/docs/boxes/versioning.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ to Vagrant makes it easy to use and fit nicely into the Vagrant workflow.
2525

2626
This page will cover how to use versioned boxes. It does _not_ cover how
2727
to update your own custom boxes with versions. That is covered in
28-
[creating a base box](/docs/boxes/base.html).
28+
[creating a base box](/docs/boxes/base).
2929

3030
## Viewing Versions and Updating
3131

‎website/pages/docs/cli/box.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ description: |-
1313

1414
**Command: `vagrant box`**
1515

16-
This is the command used to manage (add, remove, etc.) [boxes](/docs/boxes.html).
16+
This is the command used to manage (add, remove, etc.) [boxes](/docs/boxes).
1717

1818
The main functionality of this command is exposed via even more subcommands:
1919

‎website/pages/docs/cli/cloud.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -173,7 +173,7 @@ The provider create command is used to create a new provider entry on Vagrant Cl
173173
The `url` argument is expected to be a remote URL that Vagrant Cloud can use
174174
to download the provider. If no `url` is specified, the provider entry can be updated
175175
later with a url or the [upload](#cloud-provider-upload) command can be used to
176-
upload a Vagrant [box file](/docs/boxes.html).
176+
upload a Vagrant [box file](/docs/boxes).
177177

178178
## Cloud Provider Delete
179179

@@ -193,7 +193,7 @@ Vagrant Cloud with the given options.
193193

194194
**Command: `vagrant cloud provider upload ORGANIZATION/BOX-NAME PROVIDER-NAME VERSION BOX-FILE`**
195195

196-
The provider upload command will upload a Vagrant [box file](/docs/boxes.html) to Vagrant Cloud for
196+
The provider upload command will upload a Vagrant [box file](/docs/boxes) to Vagrant Cloud for
197197
the specified version and provider.
198198

199199
# Cloud Publish

‎website/pages/docs/cli/connect.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ description: |-
1313
**Command: `vagrant connect NAME`**
1414

1515
The connect command complements the
16-
[share command](/docs/cli/share.html) by enabling access to shared
16+
[share command](/docs/cli/share) by enabling access to shared
1717
environments. You can learn about all the details of Vagrant Share in the
1818
[Vagrant Share section](/docs/share/).
1919

‎website/pages/docs/cli/destroy.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,4 +36,4 @@ the box installed in the system will still be present on the hard drive. To
3636
return your computer to the state as it was before `vagrant up` command, you
3737
need to use `vagrant box remove`.
3838

39-
For more information, read about the [`vagrant box remove`](/docs/cli/box.html) command.
39+
For more information, read about the [`vagrant box remove`](/docs/cli/box) command.

‎website/pages/docs/cli/index.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,6 +27,6 @@ available by reading the appropriate sub-section available in the left
2727
navigational area of this site.
2828

2929
You may also wish to consult the
30-
[documentation](/docs/other/environmental-variables.html) regarding the
30+
[documentation](/docs/other/environmental-variables) regarding the
3131
environmental variables that can be used to configure and control
3232
Vagrant in a global way.

‎website/pages/docs/cli/machine-readable.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ is replaced with machine-friendly output.
1616

1717
This mode makes it easy to programmatically execute Vagrant and read data
1818
out of it. This output format is protected by our
19-
[backwards compatibility](/docs/installation/backwards-compatibility.html)
19+
[backwards compatibility](/docs/installation/backwards-compatibility)
2020
policy. Until Vagrant 2.0 is released, however, the machine readable output
2121
may change as we determine more use cases for it. But the backwards
2222
compatibility promise should make it safe to write client libraries to

‎website/pages/docs/cli/non-primary.mdx

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -28,8 +28,8 @@ non-primary subcommands. They're executed just like any other subcommand:
2828
The list of non-primary commands is below. Click on any command to learn
2929
more about it.
3030

31-
- [docker-exec](/docs/docker/commands.html)
32-
- [docker-logs](/docs/docker/commands.html)
33-
- [docker-run](/docs/docker/commands.html)
34-
- [rsync](/docs/cli/rsync.html)
35-
- [rsync-auto](/docs/cli/rsync-auto.html)
31+
- [docker-exec](/docs/docker/commands)
32+
- [docker-logs](/docs/docker/commands)
33+
- [docker-run](/docs/docker/commands)
34+
- [rsync](/docs/cli/rsync)
35+
- [rsync-auto](/docs/cli/rsync-auto)

‎website/pages/docs/cli/package.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ description: |-
1313
**Command: `vagrant package [name|id]`**
1414

1515
This packages a currently running _VirtualBox_ or _Hyper-V_ environment into a
16-
re-usable [box](/docs/boxes.html). This command can only be used with
16+
re-usable [box](/docs/boxes). This command can only be used with
1717
other [providers](/docs/providers/) based on the provider implementation
1818
and if the provider supports it.
1919

‎website/pages/docs/cli/port.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,4 +39,4 @@ $ vagrant port my-machine
3939

4040
- `--machine-readable` - This tells Vagrant to display machine-readable output
4141
instead of the human-friendly output. More information is available in the
42-
[machine-readable output](/docs/cli/machine-readable.html) documentation.
42+
[machine-readable output](/docs/cli/machine-readable) documentation.

‎website/pages/docs/cli/reload.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,8 +12,8 @@ description: |-
1212

1313
**Command: `vagrant reload [name|id]`**
1414

15-
The equivalent of running a [halt](/docs/cli/halt.html) followed by an
16-
[up](/docs/cli/up.html).
15+
The equivalent of running a [halt](/docs/cli/halt) followed by an
16+
[up](/docs/cli/up).
1717

1818
This command is usually required for changes made in the Vagrantfile to
1919
take effect. After making any modifications to the Vagrantfile, a `reload`

‎website/pages/docs/cli/resume.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ description: |-
1414
**Command: `vagrant resume [name|id]`**
1515

1616
This resumes a Vagrant managed machine that was previously suspended,
17-
perhaps with the [suspend command](/docs/cli/suspend.html).
17+
perhaps with the [suspend command](/docs/cli/suspend).
1818

1919
The configured provisioners will not run again, by default. You can force
2020
the provisioners to re-run by specifying the `--provision` flag.

‎website/pages/docs/cli/rsync-auto.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ description: |-
1313
**Command: `vagrant rsync-auto`**
1414

1515
This command watches all local directories of any
16-
[rsync synced folders](/docs/synced-folders/rsync.html) and automatically
16+
[rsync synced folders](/docs/synced-folders/rsync) and automatically
1717
initiates an rsync transfer when changes are detected. This command does
1818
not exit until an interrupt is received.
1919

@@ -42,7 +42,7 @@ To ensure that the command works properly, you should start `rsync-auto`
4242
only when the machine is running, and shut it down before any machine
4343
state changes.
4444

45-
You can always force a resync with the [rsync](/docs/cli/rsync.html) command.
45+
You can always force a resync with the [rsync](/docs/cli/rsync) command.
4646

4747
## Vagrantfile Changes
4848

‎website/pages/docs/cli/rsync.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ description: The "vagrant rsync" command forces a re-sync of any rsync synced fo
1010
**Command: `vagrant rsync`**
1111

1212
This command forces a re-sync of any
13-
[rsync synced folders](/docs/synced-folders/rsync.html).
13+
[rsync synced folders](/docs/synced-folders/rsync).
1414

1515
Note that if you change any settings within the rsync synced folders such
1616
as exclude paths, you will need to `vagrant reload` before this command will

‎website/pages/docs/cli/suspend.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,10 +13,10 @@ description: |-
1313
**Command: `vagrant suspend [name|id]`**
1414

1515
This suspends the guest machine Vagrant is managing, rather than fully
16-
[shutting it down](/docs/cli/halt.html) or [destroying it](/docs/cli/destroy.html).
16+
[shutting it down](/docs/cli/halt) or [destroying it](/docs/cli/destroy).
1717

1818
A suspend effectively saves the _exact point-in-time state_ of the machine,
19-
so that when you [resume](/docs/cli/resume.html) it later, it begins running
19+
so that when you [resume](/docs/cli/resume) it later, it begins running
2020
immediately from that point, rather than doing a full boot.
2121

2222
This generally requires extra disk space to store all the contents of the

‎website/pages/docs/disks/index.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -16,12 +16,12 @@ for more information on how to use and enable this feature.
1616
Vagrant Disks is a feature that allows users to define what mediums should be attached
1717
to their guests, as well as allowing users to resize their primary disk.
1818

19-
For examples on how to achieve this, among other use cases, please refer to the [usage](/docs/disks/usage.html)
19+
For examples on how to achieve this, among other use cases, please refer to the [usage](/docs/disks/usage)
2020
guide for more information!
2121

2222
For more information about what options are available for configuring disks, see the
23-
[configuration section](/docs/disks/configuration.html).
23+
[configuration section](/docs/disks/configuration).
2424

2525
## Supported Providers
2626

27-
Currently, only VirtualBox is supported. Please refer to the [VirtualBox documentation](/docs/disks/virtualbox/index.html) for more information on using disks with the VirtualBox provider!
27+
Currently, only VirtualBox is supported. Please refer to the [VirtualBox documentation](/docs/disks/virtualbox) for more information on using disks with the VirtualBox provider!

‎website/pages/docs/disks/virtualbox/index.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,5 +37,5 @@ these disks to a guests SATA Controller. It should be noted that up to 30 disks
3737
can be attached to the SATA Controller.
3838

3939
For more information on how to use VirtualBox to configure disks for a guest, refer
40-
to the [general usage](/docs/disks/usage.html) and [configuration](/docs/disks/configuration.html)
40+
to the [general usage](/docs/disks/usage) and [configuration](/docs/disks/configuration)
4141
guide for more information.

‎website/pages/docs/disks/virtualbox/usage.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ information about this flag visit the [Experimental docs page](/docs/experimenta
2525
for more info. Without this flag enabled, any disks defined will not be configured.
2626

2727
For examples of how to use the disk feature with VirtualBox, please refer to the
28-
[general disk usage guide](/docs/disks/usage.html) for more examples.
28+
[general disk usage guide](/docs/disks/usage) for more examples.
2929

3030
## provider_config options
3131

‎website/pages/docs/experimental.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -44,17 +44,17 @@ This is a list of all the valid experimental features that Vagrant recognizes:
4444
### `typed_triggers`
4545

4646
Enabling this feature allows triggers to recognize and execute `:type` triggers.
47-
More information about how these should be used can be found on the [trigger documentation page](/docs/triggers/configuration.html#trigger-types)
47+
More information about how these should be used can be found on the [trigger documentation page](/docs/triggers/configuration#trigger-types)
4848

4949
### `disks`
5050

5151
Enabling this feature will allow Vagrant to manage and configure virtual hard disks
5252
for certain providers. More information about supported providers and how to
53-
configure disks can be found on the [disk documentation page](/docs/disks/index.html)
53+
configure disks can be found on the [disk documentation page](/docs/disks)
5454

5555
### `dependency_provisioners`
5656

5757
Enabling this feature allows all provisioners to specify `before` and `after`
5858
options. These options allow provisioners to be configured to run before or after
5959
any given "root" provisioner. more information about these options can be found
60-
on the [base provisioner documentation page](/docs/provisioning/basic_usage.html)
60+
on the [base provisioner documentation page](/docs/provisioning/basic_usage)

‎website/pages/docs/index.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,10 +16,10 @@ Welcome to the documentation for Vagrant - the command line utility for managing
1616
the lifecycle of virtual machines. This website aims to document every feature
1717
of Vagrant from top-to-bottom, covering as much detail as possible. If you are
1818
just getting started with Vagrant, it is highly recommended that you start with
19-
the [getting started guide](/intro/getting-started/index.html) first, and then
19+
the [getting started guide](/intro/getting-started) first, and then
2020
return to this page.
2121

2222
The navigation will take you through each component of Vagrant. Click on a
2323
navigation item to get started, or read more about
24-
[why developers, designers, and operators choose Vagrant](/intro/index.html)
24+
[why developers, designers, and operators choose Vagrant](/intro)
2525
for their needs.

‎website/pages/docs/installation/index.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ description: |-
1212
# Installing Vagrant
1313

1414
Installing Vagrant is extremely easy. Head over to the
15-
[Vagrant downloads page](/downloads.html) and get the appropriate installer or
15+
[Vagrant downloads page](/downloads) and get the appropriate installer or
1616
package for your platform. Install the package using standard procedures for
1717
your operating system.
1818

‎website/pages/docs/installation/uninstallation.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ rm -f /usr/bin/vagrant
4545

4646
## Removing User Data
4747

48-
Removing the user data will remove all [boxes](/docs/boxes.html),
48+
Removing the user data will remove all [boxes](/docs/boxes),
4949
[plugins](/docs/plugins/), license files, and any stored state that may be used
5050
by Vagrant. Removing the user data effectively makes Vagrant think it
5151
is a fresh install.

‎website/pages/docs/installation/upgrading-from-1-0.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,12 +13,12 @@ description: |-
1313
# Upgrading From Vagrant 1.0.x
1414

1515
The upgrade process from 1.0.x to 1.x is straightforward. Vagrant is quite
16-
[backwards compatible](/docs/installation/backwards-compatibility.html)
16+
[backwards compatible](/docs/installation/backwards-compatibility)
1717
with Vagrant 1.0.x, so you can simply reinstall Vagrant
1818
over your previous installation by downloading the latest package and
1919
installing it using standard procedures for your operating system.
2020

21-
As the [backwards compatibility](/docs/installation/backwards-compatibility.html)
21+
As the [backwards compatibility](/docs/installation/backwards-compatibility)
2222
page says, **Vagrant 1.0.x plugins will not work with Vagrant 1.1+**. Many
2323
of these plugins have been updated to work with newer versions of Vagrant,
2424
so you can look to see if they've been updated. If not however, you will have

‎website/pages/docs/installation/upgrading.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -12,20 +12,20 @@ description: |-
1212
# Upgrading Vagrant
1313

1414
If you are upgrading from Vagrant 1.0.x, please read the
15-
[specific page dedicated to that](/docs/installation/upgrading-from-1-0.html).
15+
[specific page dedicated to that](/docs/installation/upgrading-from-1-0).
1616
This page covers upgrading Vagrant in general during the 1.x series.
1717

1818
Vagrant upgrades during the 1.x release series are straightforward:
1919

20-
1. [Download](/downloads.html) the new package
20+
1. [Download](/downloads) the new package
2121
2. Install it over the existing package
2222

2323
The installers will properly overwrite and remove old files. It is recommended
2424
that no other Vagrant processes are running during the upgrade process.
2525

2626
Note that Vagrantfile stability for the new Vagrantfile syntax is not
2727
promised until 2.0 final. So while Vagrantfiles made for 1.0.x will
28-
[continue to work](/docs/installation/backwards-compatibility.html),
28+
[continue to work](/docs/installation/backwards-compatibility),
2929
newer Vagrantfiles may have backwards incompatible changes until 2.0 final.
3030

3131
-> **Run into troubles upgrading?** Please [report an issue](https://github.com/hashicorp/vagrant/issues)

‎website/pages/docs/multi-machine.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -89,7 +89,7 @@ that "B" is last. That is because the ordering is outside-in, in
8989
the order of the file.
9090

9191
If you want to apply a slightly different configuration to multiple machines,
92-
see [this tip](/docs/vagrantfile/tips.html#loop-over-vm-definitions).
92+
see [this tip](/docs/vagrantfile/tips#loop-over-vm-definitions).
9393

9494
## Controlling Multiple Machines
9595

@@ -118,7 +118,7 @@ slashes, it assumes you are using a regular expression.
118118

119119
In order to facilitate communication within machines in a multi-machine setup,
120120
the various [networking](/docs/networking/) options should be used.
121-
In particular, the [private network](/docs/networking/private_network.html) can
121+
In particular, the [private network](/docs/networking/private_network) can
122122
be used to make a private network between multiple machines and the host.
123123

124124
## Specifying a Primary Machine

0 commit comments

Comments
 (0)