Fixes #2: supervisord logs available via 'docker logs'

Author: ryzy

README.md

@@ -15,6 +15,12 @@ Just add you supervisord config(s) to `/etc/supervisor.d/` directory to launch y
 
 Learn more about about [supervisord inside containers on official Docker documentation](https://docs.docker.com/articles/using_supervisord/).
 
+##### - error logging
+
+Logfile for supervisord is switched off to avoid logging inside container. Instead, all logs are easily available via `docker logs [container name]`.
+
+This is probably the best approach if you'd like to source your logs from outside the container via `docker logs` (also via CoreOS `journald') and you don't want to worry about logging and log management inside your container and/or data volume.
+
 ##### - /data volume
 
 The `/data` directory is meant to be used to simply and easily deploy web applications using a volume binding on `/data`, presumably using [data only containers](https://docs.docker.com/userguide/dockervolumes/) pattern.

supervisord.conf

@@ -1,18 +1,9 @@
 [supervisord]
 pidfile = /var/run/supervisord.pid
-logfile = /var/log/supervisor/supervisord.log
-childlogdir = /var/log/supervisor/
-
-# Do we really need to interact with supervisord?
-#[supervisorctl]
-#serverurl = unix:///var/run/supervisord.sock
-
-# inet_http_server, rpcinterface:supervisor if you want to use supervisorctl
-#[unix_http_server]
-#file = /var/run/supervisord.sock
-
-#[rpcinterface:supervisor]
-#supervisor.rpcinterface_factory = supervisor.rpcinterface:make_main_rpcinterface
+logfile = NONE
+# Set loglevel=debug, only then all logs from child services are printed out
+# to container logs (and thus available via `docker logs [container]`
+loglevel = debug
 
 [include]
 files = /etc/supervisord.d/*.conf