From eb970940b415301bd5fb72d2cb627cdd7b77b10e Mon Sep 17 00:00:00 2001 From: Axel DE VIGNON Date: Wed, 27 Sep 2017 15:52:59 +0200 Subject: [PATCH] =?UTF-8?q?[WIP]=C2=A0Readme=20in=20english?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 63d5d6b..012722d 100644 --- a/README.md +++ b/README.md @@ -132,8 +132,9 @@ You may access the VM using SSH using the `vagrant ssh` command. There is an existing Unix user: - login: vagrant - password: vagrant +This user belongs to the sudoers and may `sudo` with no password required. -The SSH identity forwarding is enabled from the host to the VM (`config.ssh.forward_agent = true`). This means that your host's computer SSH identity is forwarded to the VM. That may be useful in many cases. For example, you clone a Github repository to your host computer using the host's SSH public key attached to your Github account. With the identify forwarding enabled, you can SSH to the VM, `cd` to the downloaded repository and run a `git pull`. It will use your host computer's keypair. There is no need to add a new public key on your Github account. +The SSH identity forwarding is enabled from the host to the VM (`config.ssh.forward_agent = true`). This means that your host computer's SSH identity is forwarded to the VM. That may be useful in many cases. For example, you clone a Github repository to your host computer using the host's SSH public key attached to your Github account. With the identify forwarding enabled, you can SSH to the VM, `cd` to the downloaded repository and run a `git pull`. It will use your host computer's keypair. There is no need to add a new public key on your Github account. ### Apache