More precise README

Author: cimnine

README.md

@@ -25,19 +25,27 @@ total 16K
 -rw-r--r--  1 user 1.4K Jul 15 17:43 README.md
 -rw-r--r--  1 user  625 Jul 15 17:41 docker-compose.yml
 drwxr-xr-x 36 user 1.2K Jul 15 13:56 hitobito
--rw-r--r--  1 user  153 Jul 15 10:35 hitobito.code-workspace
 drwxr-xr-x 27 user  864 Jun 11 09:30 hitobito_generic
 drwxr-xr-x 29 user  928 Jul 15 09:43 hitobito_insieme
 ```
 
+### Exposed Ports
+
+The `docker-compose.yml` file does expose all relevant ports.
+But it does not assign them a well-known port.
+This means, that it is _intentionally_ not possible to access the main application using `http://localhost:3000`!
+Either you use `docker-compose ps` (or the `docker-compose port SERVICE PORTNUMBER` command) to get the actual port Docker assigned – or you use something like [Reception](https://github.com/nxt-engineering/reception).
+
+Why would you need this _Reception_ thingy? Because it makes all the services accessible through a reverse proxy that is accessible using `http://SERVICENAME.PROJECTNAME.docker` (or `http://SERVICENAME.PROJECTNAME.local` on Linux).
+This makes work more convenient and allows to have multiple projects, that all bind to the same port (e.g. `3000`), running at the same time.
+(Because Docker will handle the port conflict for us.)
+As an extra you get an overview over all running services and their exposed ports for free at `http://reception.docker` (or `http://reception.local` on linux).
+
 ## Docker Runtime
 
 The simplest way to work on hitobito is to use Docker:
 
 ```bash
-# First time
-docker-compose run --rm app rake db:seed wagon:seed
-
 # Every other time
 docker-compose up app
 
@@ -90,6 +98,14 @@ root@a42b42c42d42:/app/hitobito# cd ../hitobito_WAGON/
 root@a42b42c42d42:/app/hitobito_WAGON# rspec
 ```
 
+## Seed
+
+If you need to re-seed your db, use the following command:
+
+```
+docker-compose run --rm app rake db:seed wagon:seed
+```
+
 ## Full-text search
 
 Hitobito relies on Sphinx Search for indexing Persons, Events and Groups.