Re: Introducing Fineract as a Service

2020-03-31 Thread Ed Cable
Daniel, I really enjoyed seeing the demo before and thanks for sharing with the rest of the community. Have you also automated the deployment of multi-tenant instances in the PCI-compliant environment as well? Thanks, Ed On Tue, Mar 31, 2020 at 2:59 AM Daniel Liechtenstein wrote: > Dear Fine

Re: Mifos X and Fineract Training

2020-03-31 Thread Saransh Sharma
We are also launching such program in few days. On Tue, 31 Mar 2020, 01:08 Javier Borkenztain, wrote: > 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,

Re: Introducing Fineract as a Service

2020-03-31 Thread Ankit Muellner
Much needed and strategic. On Tue, 31 Mar 2020 at 11.59, Daniel Liechtenstein wrote: > Dear Fineract Community Members, > > My name is Daniel and I'm the VP bizdev of Articode, a software > development company located in Israel. I'm happy to be a part of the > community and I would like to share

Re: Introducing Fineract as a Service

2020-03-31 Thread Saransh Sharma
Beautiful This is amazing, if it is possible that you could make the background process open also definitely a big help. On Tue, 31 Mar 2020, 15:29 Daniel Liechtenstein, wrote: > Dear Fineract Community Members, > > My name is Daniel and I'm the VP bizdev of Articode, a software > development c

Introducing Fineract as a Service

2020-03-31 Thread Daniel Liechtenstein
Dear Fineract Community Members, My name is Daniel and I'm the VP bizdev of Articode, a software development company located in Israel. I'm happy to be a part of the community and I would like to share with you a cool product that we developed that any of you can use. Fineract as a Service - Auto

Re: Reopen PR for Fineract on kubernetes

2020-03-31 Thread Yemdjih Kaze Nasser
Will try that. On Tue, 31 Mar 2020 at 07:41, Michael Vorburger wrote: > 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 > t