Containerization is a lightweight alternative to full machine virtualization that involves encapsulating an application in a container with its own operating environment.
Well, now we got noPWS container with IRIS, and how to connect to it, simply, without any durable sys or files, using normal peoples way like Environment variables?
I think there have been articles published here before but I'm struggling to find them:
I'd like to be able to create my own customised version of the official IRIS Community Edition Container, eg with Node.js and a number of modules pre-installed. So, for example, can I create my own Dockerfile that begins with something like:
FROM containers.intersystems.com/intersystems/iris-community-arm64:2023.2.0.227.0
Been trying to setup a iris 4 health community version along with a webgateway bothing utilizing docker. The documentation seems a little sparse when it comes to configuring each of these to work together, especially when it comes to utilizing the Webgateway to front end the MGMT pages for Irirs 4 Health.
I know there is a github repo that has a docker compose file, but that doesn't see to provide a light on what needs to be configured in order for it to work.
It's not clear to me, when using the InterSystems Container Repository, which version is the best / most recent non-preview Community Edition version to use.
I see lots of 2023.2.x versions, a single 2023.3 and 2024.1 version, but also a latest-cd and latest-em (with no explanation as to what cd and em mean).
I assume the trick is to use one of the latest-xx ones? If so, which?
Unfortunately I haven't been able to find any explanatory information anywhere about the nomenclature conventions used.
By views
.png)