[ 
https://issues.apache.org/jira/browse/FINERACT-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17437131#comment-17437131
 ] 

Phong edited comment on FINERACT-1163 at 11/3/21, 9:46 AM:
-----------------------------------------------------------

I see that there's an updated entrypoint script that check for the database in 
[this 
commit|https://github.com/apache/fineract/commit/0de257fd44f42c5706448ccc589761604229b6a5#diff-6f9d41d046756f0ddc2fcee0626bdb50100d12b88f293734eff742818e03efa2].
 Unfortunately it uses a hardcoded hostname to the database. I have added a PR 
that make use of the environment variable instead.


was (Author: devopsepay):
I see that there's an updated entrypoint script that check for the database in 
[this 
commit|https://github.com/apache/fineract/commit/0de257fd44f42c5706448ccc589761604229b6a5#diff-6f9d41d046756f0ddc2fcee0626bdb50100d12b88f293734eff742818e03efa2].
 Unfortunately it uses a hardcoded hostname to the database. I have added a PR 
to use environment variable instead.

> fineract-server does not wait for fineractmysql to be up and running
> --------------------------------------------------------------------
>
>                 Key: FINERACT-1163
>                 URL: https://issues.apache.org/jira/browse/FINERACT-1163
>             Project: Apache Fineract
>          Issue Type: Improvement
>          Components: Build
>            Reporter: Eliott Bouvard
>            Priority: Minor
>              Labels: docker-compose
>   Original Estimate: 1.5h
>  Remaining Estimate: 1.5h
>
> When using docker-compose, fineract-server does not wait for fineractmysql, 
> therefore ending down and must be manually up again.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to