ssh key is now automatic no need to configure it

[discourse_docker.git] / README.md

diff --git a/README.md b/README.md
index 4b9b01f7860318c992b340755cc3b4bb6adb7b2b..97b5791a9e0972ab4c2032fc161f948cc2298d1c 100644 (file)
--- a/README.md
+++ b/README.md
@@ -21,11 +21,11 @@ If you do not do any of the above, as RoboCop once said, ["there will be… trou
 
 The simplest way to get started is the  **standalone** template:
 
-1. **Clone** this project from github: `git clone https://github.com/SamSaffron/discourse_docker.git /var/docker`
+1. **Clone** this project from github into `/var/docker` on your server: `git clone https://github.com/discourse/discourse_docker.git /var/docker`
 2. **Copy** the standalone sample into the containers directory: `cp samples/standalone.yml containers/app.yml`
 3. **Edit** `containers/app.yml` with your environment specific information
   - [bindings](#expose)
-  - [volumes](#volumes) (make sure you create the appropriate directories on the host)
+  - [volumes](#volumes)
 4. **Bootstrap** the image: `sudo ./launcher bootstrap app`
 5. **Start** the image: `sudo ./launcher start app`
 
@@ -109,7 +109,7 @@ Expose port 22 inside the container on port 2222 on ALL local host interfaces.
 ```
 volumes:
   - volume:
-      host: /var/docker/data
+      host: /var/docker/shared
       guest: /shared
 
 ```
@@ -149,21 +149,7 @@ For a Discourse instance to function properly Email must be set up. Use the `SMT
 
 ### Troubleshooting
 
-We strongly recommend you have ssh access to your running containers, this allows you very easily take a sneak peek at internals. The simplest way to gain access is:
-
-1. Run a terminal as root
-1. `ssh-keygen -b 2048 -t rsa -N "" -C "root's unprotected key" -f ~root/.ssh/id_rsa`
-1. Paste the contents of `~root/.ssh/id_rsa.pub` into your templates (see placeholder `YOUR_SSH_KEY` in samples)
-1. Bootstrap and run your container
-1. `./launcher ssh my_container`
-
-Or, if you're running as a regular user:
-
-1. Run a terminal
-1. `ssh-keygen -b 2048 -t rsa -N "" -C "my unprotected key" -f ~/.ssh/id_rsa`
-1. Paste the contents of `~/.ssh/id_rsa.pub` into your templates (see placeholder `YOUR_SSH_KEY` in samples)
-1. Bootstrap and run your container
-1. `./launcher ssh my_container`
+You can ssh into your container using `./launcher ssh my_container`, we will automatically set up ssh access during bootstrap.
 
 ### Security
 
@@ -171,3 +157,8 @@ Directory permissions in Linux are UID/GID based, if your numeric IDs on the
 host do not match the IDs in the guest, permissions will mismatch. On clean
 installs you can ensure they are in sync by looking at `/etc/passwd` and
 `/etc/group`, the Discourse account will have UID 1000.
+
+
+### Advanced topics
+
+- [Setting up SSL with Discourse Docker](https://meta.discourse.org/t/allowing-ssl-for-your-discourse-docker-setup/13847)