Michael Vorburger commented on FINERACT-882:

[FINERACT-845|https://issues.apache.org/jira/browse/FINERACT-845] by [~xurror] 
did this for Docker Compose, so this issue is now only about doing the same for 
our Kubernetes example.

It could be nice, but in the larger scheme of things of everything we should 
fix and do, this certainly isn't Critical anymore today, thus I'm lowering 

> Include UI in Fineract Docker Compose and Kubernetes deployments
> ----------------------------------------------------------------
>                 Key: FINERACT-882
>                 URL: https://issues.apache.org/jira/browse/FINERACT-882
>             Project: Apache Fineract
>          Issue Type: New Feature
>            Reporter: Michael Vorburger
>            Priority: Critical
>              Labels: UI, kubernetes, technical
> The Kubernetes deployment contributed in FINERACT-783 runs the Apache 
> Fineract back-end (based on Fineract's Docker Compose set-up).
> What would be really neat, for both the Kubernetes as well as the Docker 
> Compose set ups, would be if they would include a UI for Fineract as well!
> We should probably start with the (old) 
> https://github.com/openMF/community-app/ and later add the (new) 
> https://github.com/openMF/web-app/.
> The idea would be to build these UIs in Docker containers, and include them 
> in the Kubernetes deployment / Docker Compose YAMLs.  The UI should obviously 
> be pre-configured to "just work" for the back-end, so there may be some work 
> to change the URL the UI uses by default to talk to the REST services.
> There was some related work which would likely need to be completed as part 
> of this issue:
> * https://github.com/openMF/community-app/issues/3106
> * https://github.com/openMF/community-app/pull/3107
> * https://github.com/openMF/community-app/issues/3112
> FYI [~xurror], [~awasum], [~angeh]

This message was sent by Atlassian Jira

Reply via email to