From 43182c916ffcd96a1d448e1f8d0f5d138da175ad Mon Sep 17 00:00:00 2001 From: Sam Date: Wed, 14 May 2014 07:47:16 +1000 Subject: [PATCH] Revert "Add how to configure ssh access into the container" This reverts commit 5c7d0d2768a1af29ad5372f1e364c9d23a455172. --- README.md | 18 +----------------- 1 file changed, 1 insertion(+), 17 deletions(-) diff --git a/README.md b/README.md index cb71b2d..10b6f1a 100644 --- a/README.md +++ b/README.md @@ -117,21 +117,6 @@ volumes: Expose a directory inside the host inside the container. - -#### ssh: - -In order to ssh into the container instance, you need to provide root's public key on host. You can get the root's public key using `sudo cat /root/.ssh/id_rsa.pub`. Then add a new entry into `app.yml` under `params` to specify the key. - - ssh_key: ssh-rsa ROOT_PUBLIC_KEY_HERE - -If you don't have a key there, you could generate one using `ssh-keygen` - - sudo su # switch to root - cd ~ - ssh-keygen # defaults are fine. - exit # return to your own account - - ### Upgrading Discourse The Docker setup gives you multiple upgrade options: @@ -165,8 +150,7 @@ For a Discourse instance to function properly Email must be set up. Use the `SMT ### Troubleshooting -You can ssh into your container using `./launcher ssh my_container`, we will automatically set up ssh access during bootstrap. - +You can ssh into your container using `./launcher ssh my_container`, we will automatically set up ssh access during bootstrap. ### Security -- 2.25.1