Make The Definition Of Services More Flexible

[marcalwestf]

The idea of this issue is to define a needed service only once and to call it separately when needed.

Motivation
As of now, there are six docker compose files:

• docker-compose.yml
• docker-compose-auth.yml
• docker-compose-cache.yml
• docker-compose-develop.yml
• docker-compose-storage.yml
• docker-compose-vue.yml

In every one of these docker compose files, the required services are defined.
In very seldom cases, a service is called with different parameters.
Mostly, the exact same service is used in different docker compose files.
This means, if one of these services needs a change, it has to be done in every docker compose file, which is prone to errors.
For example, it can be changed in one docker compose file, but left out in anther, leaving the project inconsistent.

If implemented correctly, the service definition would be unified and the possibility of combining services increased.

Solution Suggested
The solution put forward in this issue aims at defining every required service only once in a docker compose file.
Examples of the new docker compose files:

• adempiere_site-service.yml
• postgresql-service.yml
• adempiere_zk-service.yml
• adempiere_grpc_server-service_standard.yml
• adempiere_grpc_server-service_cache.yml
• etc.

Volume and network definitions must be also considered.

Then, when calling docker compose to execute with the command
start-all.sh -d [auth, cache, develop, storage, vue, default]
the script start-all.sh would execute docker compose as follows:
docker compose -f <file1.yml> -f <file2.yml> -f <file3.yml> ... -f <file n.yml> up -d

Similar measures would take place when shutting down all services in script stop-all .sh.