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

updated links on error messages and keys readme to reflect forthcoming windows documentation

This commit is contained in:
John Bender 2010-03-25 23:07:10 -07:00
parent 2e39ab53e7
commit 51853e2e8a
2 changed files with 16 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
keys/README.md
View File

@ -13,5 +13,5 @@ and configure the private key in the Vagrantfile with
If you are using Vagrant on windows, the .ppk file contained here, in the keys directory,
has been generated from the private key and should be used to connect Putty to any VMs that
are leveraging the default key pair. See [TODO LINK]() in the documentation for more details on
using Putty with Vagrant.
are leveraging the default key pair. See [guide](http://vagrantup.com/docs/getting-started/windows.html)
in the documentation for more details on using Putty with Vagrant.

20
templates/errors.yml
View File

@ -85,12 +85,20 @@
<%= key_path %>
:ssh_unavailable_windows: |-
`vagrant ssh` isn't available on the Windows platform. The vagrant.ppk
file is available at <%= key_path %>.ppk
for use with Putty. To do this create a new Putty session for vagrant@localhost on
port <%= ssh_port %>, in the Connection>SSH>Auth configuration section navigate
to the vagrant.ppk file, select it, save the session for later use, and connect.
For a more detailed guide please consult TODO LINK.
`vagrant ssh` isn't available on the Windows platform. The
vagrant.ppk file is available at
<%= key_path %>.ppk
for use with Putty. To do this create a new Putty session for
vagrant@localhost on port <%= ssh_port %>, in the Connection>SSH>Auth
configuration section navigate to the vagrant.ppk file,
select it, save the session for later use, and connect.
For a more detailed guide please consult:
http://vagrantup.com/docs/getting-started/windows.html
:virtualbox_import_failure: |-
The VM import failed! Try running `VBoxManage import` on the box file manually for more verbose error output.
:virtualbox_invalid_version: |-