From b144be5e665b5dc68fd1b07711c0cdb85b299811 Mon Sep 17 00:00:00 2001 From: Megan Marsh Date: Wed, 9 Jan 2019 11:06:10 -0800 Subject: [PATCH] add continuation links to getting started docs --- website/source/intro/getting-started/build-image.html.md | 4 +++- website/source/intro/getting-started/install.html.md | 2 ++ website/source/intro/getting-started/parallel-builds.html.md | 2 ++ website/source/intro/getting-started/provision.html.md | 2 ++ website/source/intro/getting-started/vagrant.html.md | 2 ++ 5 files changed, 11 insertions(+), 1 deletion(-) diff --git a/website/source/intro/getting-started/build-image.html.md b/website/source/intro/getting-started/build-image.html.md index cb84cabb6..bb9f7a6a3 100644 --- a/website/source/intro/getting-started/build-image.html.md +++ b/website/source/intro/getting-started/build-image.html.md @@ -109,7 +109,7 @@ Next, let's build the image from this template. An astute reader may notice that we said earlier we'd be building an image with Redis pre-installed, and yet the template we made doesn't reference Redis anywhere. In fact, this part of the documentation will only cover making a first -basic, non-provisioned image. The next section on provisioning will cover +basic, non-provisioned image. The [next section on provisioning](./provision.html) will cover installing Redis. ## Your First Image @@ -638,4 +638,6 @@ For Windows 2016: The bootstrapping and sample provisioning should work the same across all Windows server versions. +[Continue to provisioning an image](./provision.html) + [platforms]: /docs/builders/index.html diff --git a/website/source/intro/getting-started/install.html.md b/website/source/intro/getting-started/install.html.md index eab3b5675..5ec74a504 100644 --- a/website/source/intro/getting-started/install.html.md +++ b/website/source/intro/getting-started/install.html.md @@ -130,3 +130,5 @@ On *Arch* Linux there is a package named `packer` in the main repository and in the AUR. The package `packer` in the AUR is an old name for a package management tool for Arch, it's not Hashicorp Packer. + +[Continue to building an image](./build-image.html) diff --git a/website/source/intro/getting-started/parallel-builds.html.md b/website/source/intro/getting-started/parallel-builds.html.md index ec5918da3..c0684168f 100644 --- a/website/source/intro/getting-started/parallel-builds.html.md +++ b/website/source/intro/getting-started/parallel-builds.html.md @@ -172,3 +172,5 @@ executed when you execute the command. At the end of the build, Packer outputs both of the artifacts created (an AMI and a DigitalOcean snapshot). Both images created are bare bones Ubuntu installations with Redis pre-installed. + +[Continue to Vagrant boxes](./vagrant.html) diff --git a/website/source/intro/getting-started/provision.html.md b/website/source/intro/getting-started/provision.html.md index ce2e2a043..7a7991888 100644 --- a/website/source/intro/getting-started/provision.html.md +++ b/website/source/intro/getting-started/provision.html.md @@ -101,3 +101,5 @@ saves tons of time later as you launch these images since everything is pre-installed. Additionally, since everything is pre-installed, you can test the images as they're built and know that when they go into production, they'll be functional. + +[Continue to parallel builds](./parallel-builds.html) \ No newline at end of file diff --git a/website/source/intro/getting-started/vagrant.html.md b/website/source/intro/getting-started/vagrant.html.md index 60709551b..eb5a9641b 100644 --- a/website/source/intro/getting-started/vagrant.html.md +++ b/website/source/intro/getting-started/vagrant.html.md @@ -76,3 +76,5 @@ resources of the artifact are also removed. For example, when building a VMware image, if you turn it into a Vagrant box, the files of the VMware image will be deleted since they were compressed into the Vagrant box. With creating AWS images, however, the AMI is kept around, since Vagrant needs it to function. + +[Continue to Next Steps](./next.html)