Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

implement deployment of new mifos web-app instead of the community app. #25

Open
elijah0kello opened this issue Apr 17, 2024 · 2 comments

Comments

@elijah0kello
Copy link
Collaborator

Right now, mojafos deploys a Mifos X with the old community app. We need to make it so that it deploys the latest stable release of the web app.

@elijah0kello
Copy link
Collaborator Author

@tdaly61 I think this is actually an opportunity for us to actually get rid of helm completely. We could generate k8s deployment manifests from docker-compose files.

What do you think?

@tdaly61
Copy link
Collaborator

tdaly61 commented Apr 18, 2024

@elijah0kello , I think we could/should look at this because it may provide some simplifications but what we need to be careful about is not to introduce longer term issues. I can explain when we meet next week (or never hesitate to whatsapp me or ping me to meet at anytime) but helm absolutely has its place e.g. upgrades and chart versioning and enabling complex configuration etc so we don't want to throw it out when it is useful or indeed simplifies things BUT we also do not want to use it when it makes things more complicated than they need to be. For vNow for instance there are > 37K lines of helm values.yaml settings which is tragic for end users (vnext is < 1/10th of that total yaml lines) so absolutely lets look at this !! (sorry longer answer than you probably wanted BUT you raise an important question )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants