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

Remove references to base.box, since it is no more

This commit is contained in:
Mitchell Hashimoto 2010-07-31 08:40:26 -07:00
parent 57ff845843
commit 7b376ca9ab
2 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/boxes.md
View File

@ -19,11 +19,11 @@ Boxes are also required as a base for all vagrant projects. The
Boxes can be installed from the filesystem or via HTTP (note that
if you're interested, its quite easy to extend this to support more
protocols). No matter the source, the installation method is the same.
The following adds a box named `ubuntu_base` to a local vagrant
The following adds a box named `lucid32` to a local vagrant
installation:
{% highlight bash %}
$ vagrant box add ubuntu_base http://files.vagrantup.com/base.box
$ vagrant box add lucid32 http://files.vagrantup.com/lucid32.box
{% endhighlight %}
The name used with the `vagrant box add` command is the name used to
@ -38,11 +38,11 @@ first few commands tell you to add a box named "base" to the project.
## Removing a Box
Boxes can just as easily be removed using the same `vagrant box` command.
The following command removes the `ubuntu_base` box which was added in the
The following command removes the `lucid32` box which was added in the
previous section:
{% highlight bash %}
$ vagrant box remove ubuntu_base
$ vagrant box remove lucid32
{% endhighlight %}
**Warning:** There is no going back from this command. This command literally
@ -58,7 +58,7 @@ $ vagrant box list
=====================================================================
Installed Vagrant Boxes:
base
lucid32
=====================================================================
{% endhighlight %}

4
docs/converting_password_to_key_ssh.md
View File

@ -14,7 +14,7 @@ key-based SSH.
<h3>We updated our boxes!</h3>
<p>
If you're not using a custom base box, and you're using one of the base
boxes we created (<code>getting_started.box</code>, <code>base.box</code>, etc.),
boxes we created (<code>lucid32.box</code>, <code>lucid64.box</code>, etc.)
then just remove your old box and download the new one. We updated all
of our boxes to work with <code>0.2.x</code>!
</p>
@ -85,4 +85,4 @@ $ vagrant package --include Vagrantfile
This should spit out a `package.box` file in the current working directory which
you can now re-add to your system and use. It should be a drop-in replacement for
your previously broken box.
your previously broken box.