Updated docs

Author: albertovara

docs/configuration.md

@@ -36,4 +36,58 @@ or in a config.json:
   "APPLICATION_ROOT": ""
   }
 }
-```
+```
+
+This file could contains this keywords:
+
+
+## pyms block
+
+```pyms```: all subset inside this keywords is the configuration of this library. Each keyword will be a service of our
+[Microservice class](ms_class.md). For example, we declare our microservice class as:
+
+```python
+from pyms.flask.app import Microservice
+ms = Microservice(service="my-ms", path=__file__)
+```
+and a `config.yaml` file:
+
+```yaml
+pyms:
+  requests: true
+```
+
+our object `ms` has got a attribute `requests` that is a instance of our service [requests](services.md). 
+
+## Our microservice block
+This part contains all keywords of a [Flask Configuration Handling](http://flask.pocoo.org/docs/1.0/config/) and our 
+constants of the enviroments (local configuration, staging configuration...). Take care that a Flask configuration needs
+the keywords are declared as upper case.
+
+The name of this block is defined when you create the object of [Microservice class](ms_class.md). For example, 
+
+### Example 1
+```python
+from pyms.flask.app import Microservice
+ms = Microservice(service="my-personal-microservice", path=__file__)
+```
+and a `config.yaml` file:
+
+```yaml
+my-personal-microservice:
+  DEBUG: true
+  TESTING: false
+```
+
+### Example 2
+```python
+from pyms.flask.app import Microservice
+ms = Microservice(service="ms1-api", path=__file__)
+```
+and a `config.yaml` file:
+
+```yaml
+ms1-api:
+  DEBUG: true
+  TESTING: false
+```

docs/index.md

@@ -12,4 +12,4 @@ microservices with Python.
   * Structure of a microservice project
   * Swagger and connexion
   * Tracing requests
-* [Services of Py](structure.md)
+* [Services of PyMS](structure.md)

docs/ms_class.md

@@ -29,5 +29,67 @@ And a config file like this config.yml
 my-minimal-microservice:
   APP_NAME: "Python Microservice"
 ```
+See [Configuration](configuration.md) section to know how create a configuration file.
+
+Each keyworkd in our configuration block, could be accessed in our Microservice object througth the attribute `config`.
+
+```yaml
+# Config.yml
+example-config:
+  APP_NAME: "Python Microservice"
+  foo: "var"
+  multiplevars:
+    config1: "test1"
+    config2: "test2"
+  
+```
+```python
+#app.py
+from pyms.flask.app import Microservice
+
+ms = Microservice(service="example-config", path=__file__)
+print(ms.config.APP_NAME) 
+# >> "Python Microservice"
+print(ms.config.foo) 
+# >> "bar"
+print(ms.config.multiplevars.config1) 
+# >> "test1"
+print(ms.config.multiplevars.config2) 
+# >> "test2"
+```
+
+
+
+# Looking for Configuration file
+By default, Microservice class search a config.yml in the same path. You can set a diferent route or set a json file.
+To change this path, define a environment variable `CONFIGMAP_FILE`.
+
+This way of search the configuration is useful when you work with Docker and Kubernetes. For example, you can integrate
+a configmap of Kubernetes, with this microservice and a deployment with:
+
+```yaml
+apiVersion: extensions/v1beta1
+kind: Deployment
+metadata:
+  name: my-microservice
+spec:
+  replicas: 1
+  template:
+    spec:
+      containers:
+      - name: my-microservice
+        image: ...
+        env:
+          - name: CONFIGMAP_FILE
+            value: "/usr/share/microservice/config.yaml"
+
+        volumeMounts:
+          - mountPath: /usr/share/microservice
+            name: ms-config-volume
+      volumes:
+        - name: ms-config-volume
+          configMap:
+            name: my-microservice-configmap
+```
 
 See more examples in TODO: add link

docs/services.md

@@ -1,7 +1,7 @@
 # Services
 
 Services are libraries, resources and extensions added to the Microservice in the configuration file.
-This services are created as attribute of the [Microservice class](s_class.md) to use in the code.
+This services are created as attribute of the [Microservice class](ms_class.md) to use in the code.
 
 To add a service see the [configuration section](configuration.md).
 
@@ -11,5 +11,5 @@ The actual services are:
 Extends the Microservice with [Connexion](https://github.com/zalando/connexion)
 
 ## Requests
-Extends the [requests library](http://docs.python-requests.org/en/master/) with trace headers
-and parsing JSON objects
+Extends the [requests library](http://docs.python-requests.org/en/master/) with trace headers and parsing JSON objects.
+Encapsulate common rest operations between business services propagating trace headers if configured.

docs/structure.md

@@ -13,8 +13,5 @@ This views is usually used by Kubernetes, Eureka and other systems to check if o
 ### pyms/logger
 Print logger in JSON format to send to server like Elasticsearch. Inject span traces in logger.
 
-### pyms/rest_template
-Encapsulate common rest operations between business services propagating trace headers if configured.
-
 ### pyms/tracer
 Create an injector `flask_opentracing.FlaskTracer` to use in our projects