Comments (4)
Hi @aornugent, @iamrajiv, @HarshCasper ,
Overall, I like the idea, and yes, it carries my PR a step further.
A single authoritative repository for FLINT Images Build Source Repository is something I've been rooting for for a while.
It will eliminate redundancies and ensure that the Docker images are up to speed with the current development.
What is not clear at this point (or I'm not seeing at this point) is:-
- If consideration has been made to have the build scripts - at the source repository level - update the official FLINT images Repository centrally hosted at Dockerhub i.e.
a) FLINT Base Image currently at : https://hub.docker.com/r/mojaglobal/baseimage
b) FLINT image currently: https://hub.docker.com/r/mojaglobal/flint
-
If point 1 above holds true, what is the versioning strategy for the image builds?
-
If point 1 above holds true and there is a versioning strategy, what consideration has been made to notify interested parties (i.e. parties running official flint implementations) of image updates.
To illustrate with the SLEEK Implementation case:-
- The SLEEK implementation has its own Docker Image which uses FLINT as a base image: see https://hub.docker.com/r/mojaglobal/moja.sleek
- Having proprietary modules this image is updated privately, away from the official FLINT build processes
- So whenever FLINT images are updated, maintainers of the SLEEK Image need to be updated to update their images as well.
The same case will hold for other FLINT Implementations
from flint-ui.
Tagging @HarshCasper @Tonnix - this approach seems general and can be integrated across all repos.
@Tonnix - can you please review and see if this is compatible with your PR on FLINT.Docker? I'd love to get all moja global images consolidated and updated in one place.
from flint-ui.
@iamrajiv - do you have any further proposals? I could create a DevOps team to any repos containing Dockerfiles if there's a solution to be implemented. It'll just need a design doc and execution.
from flint-ui.
@aornugent I think this issue is almost solved like we have published the images in the GitHub container registry here. Only GCBM image is left but I think to build the image for GCBM we need GCBM files as of now we are using tlazypanda/gcbm
image.
from flint-ui.
Related Issues (20)
- Feature Request: Replace current Notifications component with UI-library's Notifications component - DatePickerPoint HOT 8
- Feature Request: Replace current Notifications component with UI-library's Notifications component - CardInfoRun HOT 5
- [OSD] Feature Request: Replace current DatePicker component with UI-library's DatePicker component - DatePicker HOT 2
- [OSD] Feature Request: Replace current DatePicker component with UI-library's DatePicker component - DatePickerGCBM HOT 5
- [OSD] Feature Request: Replace current DatePicker component with UI-library's DatePicker component - DatePickerRothC HOT 2
- Feature Request: Replace current DatePicker component with UI-library's DatePicker component - DatePickerPoint HOT 10
- Feature Request: Replace current Notifications component with UI-library's Notifications component - DatePickerRothC HOT 4
- Feature Request: Replace current Notifications component with UI-library's Notifications component - point.js HOT 5
- [OSD] Feature Request: Replace current Notifications component with UI-library's Notifications component - rothc.js HOT 4
- [OSD] Feature Request: Setup Vue-3 Support in `.devcontainer.json`
- Documentation: Add min node version for local setup HOT 2
- Bug : Accordion Overlapping HOT 3
- Feature Request: Replace current Notifications component with UI-library's Notifications component - GCBM HOT 1
- Bug: The onclick funtion on the image doesn't works. It is not linkedin thus user experience gets bad HOT 3
- Feature Request: Adding a contact US form HOT 3
- Feature Request: Replace current Modal component with UI-library's Modal component - ConfigurationsRothC
- Bug: Navbar overflowing in RothC simulation configuration HOT 4
- Bug: Header of RothC configuration section is not visible in mobile view HOT 3
- Bug: Navbar overflow in Point Simulation Configuration HOT 2
- Documentation: Update the README file with installtion commands
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from flint-ui.