Re: Reopen PR for Fineract on kubernetes

2020-03-30 Thread Michael Vorburger
I'm also not able to easily reopen it. But try to just fetch your old branch, commit your fixes, and (force?) git push, maybe that will do the trick. If it doesn't, you could always locally rename the branch and push to open a new PR, and just put a comment with the new number in the previous close

Mifos X and Fineract Training

2020-03-30 Thread Javier Borkenztain
Hi Fineracters! As we go through these challenging times, we would like to encourage everyone to find the opportunities ahead of us. This is an excellent time to re-invent ourselves, deepen our knowledge base, and invest our free time wisely. Because of that, we would like to present to you our s

Re: Can long in community app

2020-03-30 Thread Eugene Adjei-Djan
thanks team finally got it resolved and can access the community app On Sun, Mar 29, 2020 at 8:57 AM Percy Enoabane wrote: > Hello Eugene > Using the community app with local Fineract 1.x platform the credential > mifos / password works for me. Even the demo > webs

Reopen PR for Fineract on kubernetes

2020-03-30 Thread Yemdjih Kaze Nasser
I managed to successfully run kubernetes deployment I've been working on a while ago. Turns out the recent changes in namings and the connection pool where at the origin of this not working. The PR (#651 ) I opened went stale for more than 30 days and i