Awesome, will try it out and with this we might be able to close kubernetes deployment
On Sun, 12 Jan 2020 at 20:52, Michael Vorburger <m...@vorburger.ch<mailto:m...@vorburger.ch>> wrote: https://github.com/apache/fineract/pull/690 fixes the problem with docker-compose... On Sat, Jan 11, 2020 at 12:04 AM Michael Vorburger <m...@vorburger.ch<mailto:m...@vorburger.ch>> wrote: Hello, yes, it appears it is actually broken, I agree. The continuous integration non regression testing for it seems to accidentially have broken as well. I'll fix both when i get a chance. Regards, Michael _______________________ Michael Vorburger http://www.vorburger.ch On Thu, Jan 9, 2020 at 2:14 PM Saransh Sharma <sara...@muellners.com<mailto:sara...@muellners.com>> wrote: We're you able to build and run 🏃💨 docker. ? I tried couple of times but it failed could not connect to mysql service. On Thu, 9 Jan 2020, 17:57 Julian Mojico, <jul...@fiter.io<mailto:jul...@fiter.io>> wrote: Hi Saransh, 1. Check mysql hostname used in you docker-compose file: FINERACT_DEFAULT_TENANTDB_HOSTNAME=fineractmysql 2. Then log mysql (using workbench or other tool) and verify hostname column is ok. select * from `mifostenant-default`.schema_version Change the hostname, port or whatever needed to match your db configuration. 3. Restart fineract and watch logs using: docker-compose logs -f tomcat Note: If you have made any changes to Dockerfile or any files within, you might need to rebuild your docker image: docker-compose up -d --build fineract-server Hope that helps. [https://fiter.io/wp-content/uploads/2018/03/fiterlogo-1.png] Julian Mojico - Developer jul...@fiter.io<mailto:jul...@fiter.io> On Mon, Jan 6, 2020 at 10:50 AM Saransh Sharma <sara...@muellners.com<mailto:sara...@muellners.com>> wrote: Yes indeed it does fail, I tried many times seems like it's failing to connect with mysql instance. To me it seems like something related to networking. On Sat, 4 Jan 2020, 05:48 Michael Vorburger, <m...@vorburger.ch<mailto:m...@vorburger.ch>> wrote: On Fri, 3 Jan 2020, 21:17 Yemdjih Kaze Nasser, <kazenas...@gmail.com<mailto:kazenas...@gmail.com>> wrote: I don't have a particular configuration. I used the default configuration from the develop branch of the repo On Fri, Jan 3, 2020, 12:54 PM Ngadou Yopa <yopasylves...@gmail.com<mailto:yopasylves...@gmail.com>> wrote: Hi Yemdjih I noticed your unanswered message. Could you please link to your docker-compose.yml settings ? Ngadou On Sat, 21 Dec 2019, 07:45 Yemdjih Kaze Nasser, <kaze.nas...@outlook.com<mailto:kaze.nas...@outlook.com>> wrote: Just tried to run the new docker deployment and it fails It usually works. Note that we actually even have continuous integration non regression testing for it, check out https://github.com/apache/fineract/blob/develop/.travis.yml to serve fineract server. the logs mention a failure to connect to database. Could you please post the output of docker log for the application container on e.g. a GitHub gist or the Fedora Pastebin or some such place, and share a link, so that someone can have a closer look? Not sure how the environment variables work with this new setup. Steps to reproduce: docker-compose build docker-compose up -d as is described in the README. Perhaps others reading this would like to try it and chime into the conversation to confirm that it does indeed work as advertised for them? Solving this may help with the kubernetes deployment I'm working on -- [https://fiter.io/wp-content/uploads/2018/03/fiterlogo-1.png] Julian Mojico - Developer jul...@fiter.io<mailto:jul...@fiter.io>
