haskal
/
vagrant
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Adds previous and next buttons to getting started guide

This commit is contained in:
HerrBertling 2014-12-19 16:38:56 +01:00
parent 2dd4ab3913
commit 60e76caedd
11 changed files with 38 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
website/docs/source/v2/getting-started/boxes.html.md
View File

@ -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.
<a href="/v2/getting-started/project_setup.html" class="button inline-button prev-button">Project Setup</a>
<a href="/v2/getting-started/up.html" class="button inline-button next-button">Up And SSH</a>

2
website/docs/source/v2/getting-started/index.html.md
View File

@ -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.
<a href="/v2/getting-started/project_setup.html" class="button inline-button next-button">Project Setup</a>

3
website/docs/source/v2/getting-started/networking.html.md
View File

@ -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.
<a href="/v2/getting-started/provisioning.html" class="button inline-button prev-button">Provisioning</a>
<a href="/v2/getting-started/share.html" class="button inline-button next-button">Share</a>

3
website/docs/source/v2/getting-started/project_setup.html.md
View File

@ -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.
<a href="/v2/getting-started/index.html" class="button inline-button prev-button">Getting Started</a>
<a href="/v2/getting-started/boxes.html" class="button inline-button next-button">Boxes</a>

2
website/docs/source/v2/getting-started/providers.html.md
View File

@ -35,3 +35,5 @@ flags necessary.
For more information on providers, read the full documentation on
[providers](/v2/providers/index.html).
<a href="/v2/getting-started/rebuild.html" class="button inline-button prev-button">Rebuild</a>

3
website/docs/source/v2/getting-started/provisioning.html.md
View File

@ -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.
<a href="/v2/getting-started/synced_folders.html" class="button inline-button prev-button">Synced Folders</a>
<a href="/v2/getting-started/networking.html" class="button inline-button next-button">Networking</a>

3
website/docs/source/v2/getting-started/rebuild.html.md
View File

@ -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.
<a href="/v2/getting-started/teardown.html" class="button inline-button prev-button">Teardown</a>
<a href="/v2/getting-started/providers.html" class="button inline-button next-button">Providers</a>

3
website/docs/source/v2/getting-started/share.html.md
View File

@ -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).
<a href="/v2/getting-started/networking.html" class="button inline-button prev-button">Networking</a>
<a href="/v2/getting-started/teardown.html" class="button inline-button next-button">Teardown</a>

3
website/docs/source/v2/getting-started/synced_folders.html.md
View File

@ -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.
<a href="/v2/getting-started/up.html" class="button inline-button prev-button">Up And SSH</a>
<a href="/v2/getting-started/provisioning.html" class="button inline-button next-button">Provisioning</a>

3
website/docs/source/v2/getting-started/teardown.html.md
View File

@ -39,3 +39,6 @@ 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.
<a href="/v2/getting-started/share.html" class="button inline-button prev-button">Share</a>
<a href="/v2/getting-started/rebuild.html" class="button inline-button next-button">Rebuild</a>

3
website/docs/source/v2/getting-started/up.html.md
View File

@ -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.
<a href="/v2/getting-started/boxes.html" class="button inline-button prev-button">Boxes</a>
<a href="/v2/getting-started/synced_folders.html" class="button inline-button next-button">Synced Folders</a>