Hi Rohit,

Are you talking wrt Fineract 1.x or Fineract CN. There are two projects
withing Apache Fineract. Mike, it seems Rohit is talking about Fineract CN.

I think it will be great to upgrade Spring Boot and Spring versions for
Fineract CN before looking into any of the points discussed above. Maybe
start with upgrading to gradle 5 ot 6.


Thanks
Awasum




On Tue, Jan 14, 2020 at 8:46 PM Michael Vorburger <[email protected]> wrote:

> Hi,
>
> On Tue, 14 Jan 2020, 10:52 Rohit Verma, <[email protected]>
> wrote:
>
>> Hi Mike,
>>
>> Actually we already have a way to build java project based on distroless
>> based on distroless and within our fineract forks we are using that only,
>> at this stage its just a matter of pull request.
>>
>
> Oh, if you've already done it, then yes by all means do send a PR -
> looking forward to reviewing it!
>
> Usually for all the forks setting up ci/cd is very essential and the way
>> travis-ci limiting the free build minutes even on public projects, it
>> creates challenges for the fork.
>>
>
> We haven't had any capacity issues with the current CI set-up for
> http://GitHub.com/apache/fineract, but if we do, we could certainly look
> at alternatives.
>
> With github-ci we have abstracted the fork specific logic to github
>> secrets, so every fork can be used to push and deploy resources in
>> different repos and on PR there won't be a diff.
>>
>> Again I understand this is very low priority since we are talking about
>> big framework level changes. This probably would be coming through some
>> interns by the way :)
>>
>> Regards
>> Rohit
>>
>> On Tue, Jan 14, 2020 at 2:59 PM Michael Vorburger <[email protected]>
>> wrote:
>>
>>> Hello Rohit,
>>>
>>> Welcome to the Apache Fineract community!
>>>
>>> On Tue, Jan 14, 2020 at 9:26 AM Rohit Verma
>>> <[email protected]> wrote:
>>>
>>>> Hi Team,
>>>>
>>>> We are building over fineract a banking product. There are few things
>>>> which we want to discuss and get opinions from the experience developers.
>>>>
>>>> 1. Opinion on integrating with service-mesh functionalities, We are
>>>> looking forward to integrate, spring-cloud-kubernetes-istio to handle
>>>> discovery, config etc as well as to expose metrics.
>>>>
>>>> 2. Wondering if aunbis can be replaced with jwt based
>>>> authentication/authorization in conjunction of authentication adapter like
>>>> aws-cognito or auth0 or okta etc. This will reduce the usage of permissible
>>>> feign client, simplify local demos.
>>>>
>>>> 3. A faster containerization process leveraging github actions and
>>>> buildx cache
>>>>
>>>
>>> you probably already saw that we currently use TravisCI for building,
>>> including validating the container build, and then Docker Hub Builds for
>>> actually producing the container in that registry. While I'm sure like
>>> anything that process could be further optimized, "it works" as is, so I'm
>>> not sure it's "worth it" to spend time on that, compared to other things
>>> which would add value. Like why would we? Just to shave a few minutes off
>>> the build times? Who cares, given so many other things which you could do
>>> that would add real value. I don't want to (and cannot ;-) stop you from
>>> innovating on this front, but that probably would be a very low priority,
>>> for me. Providing you this feedback only because you asked for it! :-)
>>>
>>> BTW GitHub actions *are* cool - FYI
>>> https://issues.apache.org/jira/browse/FINERACT-829
>>>
>>>
>>>> with more hardened base image like distroless.
>>>>
>>>
>>> Now THAT is entirely different - contributions on this front would be
>>> very very welcome!
>>>
>>> I've written up some thoughts about this on
>>> https://issues.apache.org/jira/browse/FINERACT-830 - would you like to
>>> contribute that?
>>>
>>> 4. Building/integrating an opinionated risk assessment workflow during
>>>> loan creation process.
>>>>
>>>> Please let me know your thoughts on this. Any other unrelated
>>>> recommendations are also highly appreciated.
>>>>
>>>> Regards
>>>> Rohit
>>>>
>>>
>>> We look forward to your contributions.
>>>
>>> Best,
>>> M.
>>> _______________________
>>> Michael Vorburger
>>> http://www.vorburger.ch
>>>
>>>
>>

Reply via email to