adempiere/adempiere-ui-gateway

Default Gateway for ADempiere UI

adempiere-ui-gateway's Issues

Update README.md file

Since commit 5efd8e1 , there are several improvements, configuration and administration modifications that have to be documented in README.md.

Dkron is not displayed in browsers

As of now, the dkron is not displayed on browsers.
In the definition of the dkron service, no ports are defined, i.e. the defaults are taken.

Test # 1

Result:
When the tests are done with the present parameters, the browser is only displayed if we use the Container IP and the port 8080

• http://0.0.0.0:8899/dashboard     Firefox can’t establish a connection to the server at 0.0.0.0:8899.
• http://0.0.0.0:8899     Firefox can’t establish a connection to the server at 0.0.0.0:8899.
• http://0.0.0.0:8899/ui     status 502 message "Bad gateway"

---

• http://0.0.0.0:8080/dashboard/     Firefox can’t establish a connection to the server at 0.0.0.0:8080.
• http://0.0.0.0:8080     Firefox can’t establish a connection to the server at 0.0.0.0:8080.
• http://0.0.0.0:8080/ui     Firefox can’t establish a connection to the server at 0.0.0.0:8080

---

• http:// CONTAINER IP:8899/dashboard/     Firefox can’t establish a connection to the server at 192.168.100.4:8899.
• http:// CONTAINER IP:8899     Firefox can’t establish a connection to the server at 192.168.100.4:8899
• http:// CONTAINER IP/ui     An error occurred during a connection to 192.168.100.4
• http:// CONTAINER IP:8899/ui     Firefox can’t establish a connection to the server at 192.168.100.4:8899

---

• http:// CONTAINER IP:8080/dashboard/     404 page not found
• http:// CONTAINER IP:8080     The dkron page is displayed on the browser!!!!
• http:// CONTAINER IP:8080/ui     The dkron page is displayed on the browser!!!!

---

• http:// HOST IP:8899/ui/     Firefox can’t establish a connection to the server at 192.168.1.6:8899
• http://api.adempiere.io:8899     Firefox can’t establish a connection to the server at api.adempiere.io:8899
• http://localhost:8899     Firefox can’t establish a connection to the server at localhost:8899:

Synchronize Timezone and Localtime of All Containers with the Timezone and Localtime of Host

There are still some containers in some Docker Compose files that do not define volumes to synchronize their timezone and localtime with the one of the host (server).

Migrate Docker Compose Cache and Storage Files

The Docker Compose files docker-compose-cache.yaml and docker-compose-storage.yaml have not been synchronized to the new .env and env_template files.

This means, they do not work as of now.

Also, docker-compose-storage.yaml will be renamed to docker-compose-storage.yml, and docker-compose-vue.yaml to docker-compose-vue.yml, to avoid confusions.

Differences between configuration files

Both files .env and env_template.env differ in the definition of KAFKA_PORT:

File env_template.env:

File .env:

It seems the definition of env_template.env is more correct.

Complete services to develop operating mode

The develop operating mode is for testing.
All available services should be available and also the services should be accessible via port.

Right now, some services are missing.

Make The Definition Of Services More Flexible

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.

Service Start Fails for Envoy Proxy Definition for Processors/Backend

@EdwinBetanc0urt this maybe of interest to you:

When starting all services with
docker-compose/start-all.sh

there is an error starting the Container adempiere-ui-gateway.envoy.grpc.proxy:

When watching the container log, it shows the following:

{"log":"[2024-05-31 01:03:43.752][10][info][config] [source/server/configuration_impl.cc:130] loading 2 cluster(s)\n","stream":"stderr","time":"2024-05-31T07:03:43.75264586Z"}
{"log":"[2024-05-31 01:03:43.762][10][info][config] [source/server/configuration_impl.cc:138] loading 2 listener(s)\n","stream":"stderr","time":"2024-05-31T07:03:43.762954564Z"}

{"log":"[2024-05-31 01:03:43.864][10][critical][main] [source/server/server.cc:414] error initializing config ' /etc/envoy/envoy.yaml': transcoding_filter: Could not find 'order.Order' in the proto descriptor\n","stream":"stderr","time":"2024-05-31T07:03:43.864912823Z"}

{"log":"[2024-05-31 01:03:43.865][10][info][main] [source/server/server.cc:1029] exiting\n","stream":"stderr","time":"2024-05-31T07:03:43.865214771Z"}
{"log":"transcoding_filter: Could not find 'order.Order' in the proto descriptor\n","stream":"stderr","time":"2024-05-31T07:03:43.867317781Z"}
(END)

Seems that a the Order definition is missing.

Parametrize which Docker Compose file will be executed

Depending on the final usage, the project has different docker-compose files:

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

Additionally, the file start-all.sh is a shell script used to -among other things- start all services.

The idea is to combine both: call the shell script start-all.sh with parameters so that the desired docker-compose file is used.

At implementation, it must be remembered that if docker-compose up is called with a specific file, so must also docker-compose down.

Start services:
docker-compose -f <DOCKER_COMPOSE_FILE> up -d

Stop services:
docker-compose -f <DOCKER_COMPOSE_FILE> down

Add Kafdrop to Kafka

Kafdrop (https://github.com/obsidiandynamics/kafdrop) is a tool to administer topics, partitions, records, user groups, etc. in Kafka.

Though it is not recommended to use it in a production stack, it may be of great help when testing or debugging.

In our case, it would be added to the "develop" stack.