Michael Vorburger created FINERACT-1454:
-------------------------------------------
Summary: Container should not assume that DB hostname is
fineractmysql (and port 3306)
Key: FINERACT-1454
URL: https://issues.apache.org/jira/browse/FINERACT-1454
Project: Apache Fineract
Issue Type: Bug
Reporter: Michael Vorburger
Assignee: Michael Vorburger
Fix For: 1.6.0
See [https://github.com/vorburger/www.fineract.dev/issues/8] for
[https://www.fineract.dev|https://www.fineract.dev/] for more background:
There is a (new)
[https://github.com/apache/fineract/blob/develop/entrypoint.sh] script. It was
introduced by @victorromero in
[apache/fineract#1930|https://github.com/apache/fineract/pull/1930] for
FINERACT-1416. That script, as-is currently, because the
[{{Dockerfile}}|https://github.com/apache/fineract/blob/develop/Dockerfile] has
an {{{}ENTRYPOINT /entrypoint.sh{}}}, makes a hard-coded assumption that anyone
using the Fineract container anywhere uses {{fineractmysql 3306}} as the
hostname and port of the DB. That is not always the case; e.g. on
[https://www.fineract.dev|https://www.fineract.dev/], and I bet in some other
deployments as well, DB just so happens to not be reachable by
{{fineractmysql}} hostname.
That (new) {{entrypoint.sh}} script really must respect those Fineract official
DB configuration parameters, as seen e.g. in
[https://github.com/apache/fineract/blob/03a8a9858d1c3db703675ebaeb0828863d8b35de/docker-compose.yml]
and
[https://github.com/apache/fineract/blob/03a8a9858d1c3db703675ebaeb0828863d8b35de/kubernetes/fineract-server-deployment.yml].
I'll raise a PR with a proposed fix for this.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
