demystifying-containers VS dem

GitHub repository: https://github.com/axem-solutions/dem And detailed documentation: https://axemsolutions.io/dem_doc/

If you are open to giving it another shot, we'd greatly appreciate it: https://github.com/axem-solutions/dem

A projekt maga itt érhető el: https://github.com/axem-solutions/dem

We also faced this issue several times. The situation gets even more complicated if you work on other projects simultaneously. Our solution was the containerization of the tools ( similar way as someone already described here). We tried to create a separate container image for every tool. Sometimes these tools interfered with each other (e.g. they used the same environment variable name with different meanings), so this way we could isolate them. Separate images also mean that you don’t need to rebuild the image if you’d like to change something (e.g. use st-link instead of j-link), just swap the images. We stored the images in a registry, which then acted as a software catalog. We solved a bunch of problems this way, but we still needed a method to manage the tool images. Our idea was to group together the images required for a specific project into a “Development Environment”. We finally implemented a tool, which the developers can use to self-serve the Development Environment for the project they would like to work on. We open-sourced this management tool a couple of weeks ago, you can find it here: https://github.com/axem-solutions/dem In the next version, we would like to add support for 3rd party (or self-hosted) registries and offline usage, so if you are interested I’d be happy to help with it.

To support this approach, I wanted to share our open-source command-line tool named DEM, designed to handle containerized development environments: https://github.com/axem-solutions/dem