new configuration files
Now, configuration files are pretty complex with a lot of dependencies with the other modules and the infrastructure. Everything "hardcoded" with multiple configuration files depending on each infrastructure/environment: development, production, heroku, fiware. There is no way of creating a good container/microservice with this.
The ideas is to have a basic configuration file with more static info: version, contacting emails, etc. Everything that will depend on the environment or infrastructure like other services hosts, ips, etc goes to other configuration file. For development this file could be manually configured, but for developments this configuration file will be passed as a volumen to the container. So, environment configuration rely on a file outside the container (and outside this git repository).
Other important information will be also passed in that way and it will be not included in the repository. For example: ssl certificates needs to be something external and cannot be stored inside a git repository (for obvious security reasons). Certificates are passed to the container. Different Docker platforms (Rancher, Kubernetes, Swarm...) allows to store "secrets" and make them available to containers through different linking mechanisms.
At the same time configuration will be simplified (if possible(.