IPM/ZPM and IRIS Docker Dev Template

[mdavidovichHst]

Overall, I'm confused about the use of IPM in the irisscript that Dockerfile runs in the template. If my intent is to build a Docker image of my application with IRIS as the base image, why would I want to use IPM? In that case I don't need to package my application because it's not being shipped as a package, rather it's an image.

I will attempt to answer my own question however: I think the template is meant more for dev work with the intention of packing it, not for building a new image. If a dev just wanted to quickly bring up an IRIS instance, develop and push it out to open-exchange this would be a useful template.

That said, why is zpm in the iris script. Would you want that to run after you've developed?

[mdavidovichHst]

@evshvarov reponded:

we can take it offline and talk about IPM in community templates. But long story short - I think for 99% of projects that consists of InterSystems code elements it is make a lot of sense to follow IPM-package first approach. Even if you don't plan to use you own IPM registries. There are a lot of advantages starting from automatic tests and git-source control for interoperability UI elements and more.

@timleavitt responded:

IPM is a great tool for "I have some IRIS code on the filesystem and want to load it into the database, maybe with some additional configuration steps" and that's its main use in those sample repos.