diff options
| author | Micah Anderson <micah@riseup.net> | 2013-12-04 12:22:45 -0500 |
|---|---|---|
| committer | Micah Anderson <micah@riseup.net> | 2013-12-04 12:22:45 -0500 |
| commit | 5838e418d14ee2aa15d1bbd204a9076b8df0cccd (patch) | |
| tree | c9b6c4f68662c40761a3c260d5dcd008973e5ab1 | |
| parent | a2b1cc3cf2cc1b3e44c77a8a7fba0834cead83b7 (diff) | |
adjust vagrant custom configuration line for enabling gui for v2 vagrant config blocks
| -rw-r--r-- | docs/platform/development.md | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/docs/platform/development.md b/docs/platform/development.md index 2162bfa..2f13df6 100644 --- a/docs/platform/development.md +++ b/docs/platform/development.md @@ -154,10 +154,11 @@ 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 your -$HOME/.leaprc: +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' + @custom_vagrant_vm_line = 'config.vm.provider "virtualbox" do |v| + v.gui = true +end' and then start, or restart, your local Vagrant node. You should get a VirtualBox graphical interface presented to you showing you the bootup and eventually the login. |