From 60e76caedd04ae1dbd70db47ea708111a79c299f Mon Sep 17 00:00:00 2001 From: HerrBertling Date: Fri, 19 Dec 2014 16:38:56 +0100 Subject: [PATCH] Adds previous and next buttons to getting started guide --- .../source/v2/getting-started/boxes.html.md | 3 +++ .../source/v2/getting-started/index.html.md | 2 ++ .../v2/getting-started/networking.html.md | 3 +++ .../v2/getting-started/project_setup.html.md | 3 +++ .../source/v2/getting-started/providers.html.md | 2 ++ .../v2/getting-started/provisioning.html.md | 3 +++ .../source/v2/getting-started/rebuild.html.md | 3 +++ .../source/v2/getting-started/share.html.md | 3 +++ .../v2/getting-started/synced_folders.html.md | 3 +++ .../source/v2/getting-started/teardown.html.md | 17 ++++++++++------- .../docs/source/v2/getting-started/up.html.md | 3 +++ 11 files changed, 38 insertions(+), 7 deletions(-) diff --git a/website/docs/source/v2/getting-started/boxes.html.md b/website/docs/source/v2/getting-started/boxes.html.md index 7ed1f83d7..9d165d2ad 100644 --- a/website/docs/source/v2/getting-started/boxes.html.md +++ b/website/docs/source/v2/getting-started/boxes.html.md @@ -72,3 +72,6 @@ feature to allow you to find the box you care about. In addition to finding free boxes, HashiCorp's Atlas lets you host your own boxes, as well as private boxes if you intend on creating boxes for your own organization. + +Project Setup +Up And SSH diff --git a/website/docs/source/v2/getting-started/index.html.md b/website/docs/source/v2/getting-started/index.html.md index 687294274..812e1754e 100644 --- a/website/docs/source/v2/getting-started/index.html.md +++ b/website/docs/source/v2/getting-started/index.html.md @@ -54,3 +54,5 @@ comfort of your own machine. The rest of this guide will walk you through setting up a more complete project, covering more features of Vagrant. + +Project Setup diff --git a/website/docs/source/v2/getting-started/networking.html.md b/website/docs/source/v2/getting-started/networking.html.md index 150b4cab1..69ac4c3fc 100644 --- a/website/docs/source/v2/getting-started/networking.html.md +++ b/website/docs/source/v2/getting-started/networking.html.md @@ -43,3 +43,6 @@ Vagrant also has other forms of networking, allowing you to assign a static IP address to the guest machine, or to bridge the guest machine onto an existing network. If you're interested in other options, read the [networking](/v2/networking/index.html) page. + +Provisioning +Share diff --git a/website/docs/source/v2/getting-started/project_setup.html.md b/website/docs/source/v2/getting-started/project_setup.html.md index e36fac01c..1a2029bd1 100644 --- a/website/docs/source/v2/getting-started/project_setup.html.md +++ b/website/docs/source/v2/getting-started/project_setup.html.md @@ -36,3 +36,6 @@ set up Vagrant for an existing project. The Vagrantfile is meant to be committed to version control with your project, if you use version control. This way, every person working with that project can benefit from Vagrant without any upfront work. + +Getting Started +Boxes diff --git a/website/docs/source/v2/getting-started/providers.html.md b/website/docs/source/v2/getting-started/providers.html.md index abda2deec..9dfd31d71 100644 --- a/website/docs/source/v2/getting-started/providers.html.md +++ b/website/docs/source/v2/getting-started/providers.html.md @@ -35,3 +35,5 @@ flags necessary. For more information on providers, read the full documentation on [providers](/v2/providers/index.html). + +Rebuild diff --git a/website/docs/source/v2/getting-started/provisioning.html.md b/website/docs/source/v2/getting-started/provisioning.html.md index ad2b24150..ceb79e82d 100644 --- a/website/docs/source/v2/getting-started/provisioning.html.md +++ b/website/docs/source/v2/getting-started/provisioning.html.md @@ -75,3 +75,6 @@ directory, which is the default synced folder setup by Vagrant. You can play around some more by creating some more files and viewing them from the terminal, but in the next step we'll cover networking options so that you can use your own browser to access the guest machine. + +Synced Folders +Networking diff --git a/website/docs/source/v2/getting-started/rebuild.html.md b/website/docs/source/v2/getting-started/rebuild.html.md index aa5a3bc40..1555ca6b5 100644 --- a/website/docs/source/v2/getting-started/rebuild.html.md +++ b/website/docs/source/v2/getting-started/rebuild.html.md @@ -15,3 +15,6 @@ $ vagrant up That's it! Since the Vagrant environment is already all configured via the Vagrantfile, you or any of your coworkers simply have to run a `vagrant up` at any time and Vagrant will recreate your work environment. + +Teardown +Providers diff --git a/website/docs/source/v2/getting-started/share.html.md b/website/docs/source/v2/getting-started/share.html.md index 694bd5d15..46cde9c70 100644 --- a/website/docs/source/v2/getting-started/share.html.md +++ b/website/docs/source/v2/getting-started/share.html.md @@ -54,3 +54,6 @@ the URL again to verify that your environment is no longer being shared. Vagrant Share is much more powerful than simply HTTP sharing. For more details, see the [complete Vagrant Share documentation](/v2/share/index.html). + +Networking +Teardown diff --git a/website/docs/source/v2/getting-started/synced_folders.html.md b/website/docs/source/v2/getting-started/synced_folders.html.md index 11612e84c..80c42c876 100644 --- a/website/docs/source/v2/getting-started/synced_folders.html.md +++ b/website/docs/source/v2/getting-started/synced_folders.html.md @@ -40,3 +40,6 @@ the folders in sync. With [synced folders](/v2/synced-folders/index.html), you can continue to use your own editor on your host machine and have the files sync into the guest machine. + +Up And SSH +Provisioning diff --git a/website/docs/source/v2/getting-started/teardown.html.md b/website/docs/source/v2/getting-started/teardown.html.md index 764de1969..04ce15f9f 100644 --- a/website/docs/source/v2/getting-started/teardown.html.md +++ b/website/docs/source/v2/getting-started/teardown.html.md @@ -23,19 +23,22 @@ work. The downside is that the virtual machine still eats up your disk space, and requires even more disk space to store all the state of the virtual machine RAM on disk. -**Halting** the virtual machine by calling `vagrant halt` will gracefully -shut down the guest operating system and power down the guest machine. -You can use `vagrant up` when you're ready to boot it again. The benefit of -this method is that it will cleanly shut down your machine, preserving the +**Halting** the virtual machine by calling `vagrant halt` will gracefully +shut down the guest operating system and power down the guest machine. +You can use `vagrant up` when you're ready to boot it again. The benefit of +this method is that it will cleanly shut down your machine, preserving the contents of disk, and allowing it to be cleanly started again. The downside is that it'll take some extra time to start from a cold boot, and the guest machine still consumes disk space. -**Destroying** the virtual machine by calling `vagrant destroy` will remove -all traces of the guest machine from your system. It'll stop the guest machine, -power it down, and remove all of the guest hard disks. Again, when you're ready to +**Destroying** the virtual machine by calling `vagrant destroy` will remove +all traces of the guest machine from your system. It'll stop the guest machine, +power it down, and remove all of the guest hard disks. Again, when you're ready to work again, just issue a `vagrant up`. The benefit of this is that _no cruft_ is left on your machine. The disk space and RAM consumed by the guest machine is reclaimed and your host machine is left clean. The downside is that `vagrant up` to get working again will take some extra time since it has to reimport the machine and reprovision it. + +Share +Rebuild diff --git a/website/docs/source/v2/getting-started/up.html.md b/website/docs/source/v2/getting-started/up.html.md index 3a9686afa..f1e59a6cf 100644 --- a/website/docs/source/v2/getting-started/up.html.md +++ b/website/docs/source/v2/getting-started/up.html.md @@ -33,3 +33,6 @@ virtual machine. Cool. When you're done fiddling around with the machine, run `vagrant destroy` back on your host machine, and Vagrant will remove all traces of the virtual machine. + +Boxes +Synced Folders