diff options
| author | Micah Anderson <micah@riseup.net> | 2013-12-04 12:04:32 -0500 |
|---|---|---|
| committer | Micah Anderson <micah@riseup.net> | 2013-12-04 12:04:42 -0500 |
| commit | a2b1cc3cf2cc1b3e44c77a8a7fba0834cead83b7 (patch) | |
| tree | 55c7e8327f01367d2eaedcefcb5aae0c2fd094d4 /docs/platform/development.md | |
| parent | 74a8f354deaec027022ac6c349622f915897712b (diff) | |
fix typo
Diffstat (limited to 'docs/platform/development.md')
| -rw-r--r-- | docs/platform/development.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/platform/development.md b/docs/platform/development.md index 3c3e5bb..2162bfa 100644 --- a/docs/platform/development.md +++ b/docs/platform/development.md @@ -154,7 +154,7 @@ You can connect to your local nodes just like you do with normal LEAP nodes, by However, if you cannot connect to your local node, because the networking is not setup properly, or you have deployed a firewall that locks you out, you may need to access the graphical console. -In order to do that, you will need to configure Vagrant to launch a graphical console and then you can login as root there to diagnose the networking problem. To do this, add the following to you +In order to do that, you will need to configure Vagrant to launch a graphical console and then you can login as root there to diagnose the networking problem. To do this, add the following to your $HOME/.leaprc: @custom_vagrant_vm_line = 'config.vm.boot_mode = :gui' |