All
Accepted answers
Evgeny Shvarov · Oct 19, 2020 go to post

And we updated the images with ZPM 0.2.7 too:

intersystemsdc/iris-community:2020.3.0.221.0-zpm

intersystemsdc/iris-community:2020.4.0.524.0-zpm

intersystemsdc/iris-ml-community:2020.3.0.302.0-zpm

intersystemsdc/irishealth-community:2020.3.0.221.0-zpm

intersystemsdc/irishealth-community:2020.4.0.524.0-zpm

intersystemsdc/iris-community-arm64:2020.4.0.524.0-zpm

intersystemsdc/irishealth-community-arm64:2020.4.0.524.0-zpm

And to launch IRIS do:

docker run --rm --name my-iris -d --publish 9091:1972 --publish 9092:52773 intersystemsdc/iris-community:2020.3.0.221.0-zpm

docker run --rm --name my-iris -d --publish 9091:1972 --publish 9092:52773 intersystemsdc/iris-community:2020.4.0.524.0-zpm

docker run --rm --name my-iris -d --publish 9091:1972 --publish 9092:52773 intersystemsdc/iris-ml-community:2020.3.0.302.0-zpm

docker run --rm --name my-iris -d --publish 9091:1972 --publish 9092:52773 intersystemsdc/irishealth-community:2020.3.0.221.0-zpm

docker run --rm --name my-iris -d --publish 9091:1972 --publish 9092:52773 intersystemsdc/irishealth-community:2020.4.0.524.0-zpm

docker run --rm --name my-iris -d --publish 9091:1972 --publish 9092:52773 intersystemsdc/iris-community-arm64:2020.4.0.524.0-zpm

docker run --rm --name my-iris -d --publish 9091:1972 --publish 9092:52773 intersystemsdc/irishealth-community-arm64:2020.4.0.524.0-zpm 

And for terminal do:

docker exec -it my-iris iris session IRIS

and to start the control panel:

http://localhost:9092/csp/sys/UtilHome.csp

To stop and destroy container do:

docker stop my-iris
Evgeny Shvarov · Oct 14, 2020 go to post

While we are building a maven distribution channel the latest IRIS JDBC driver could be downloaded from here

Evgeny Shvarov · Oct 9, 2020 go to post

You can take any frontend framework you like: vue.js, React JS, Angular, and many, many more.

Evgeny Shvarov · Oct 9, 2020 go to post

CSP is fine and prooved its efficiency!

But if you compare it with REST - REST API is better, cause you have advantages of Open API (API First approach) and API Management.

Evgeny Shvarov · Oct 9, 2020 go to post

Actually, you even can avoid the customization at all,  just running the iris container together with the node.js server and frontend using docker compose.

But maybe this template will give you some thoughts.

Evgeny Shvarov · Oct 9, 2020 go to post

Rob, there is a logic of course behind every technology bonus of the contest. Technology bonuses are to encourage the usage of technology we invest in and approaches we consider promising and productive in development with InterSystems IRIS.

With REST-API, jdbc, native-api bonuses we support different ways to communicate with IRIS which we consider perspective and continuously improve. E.g. we don't engage the legacy CSP approach as you can see. How does mg-dbx talk to IRIS in the end?

Docker bonus is to support the "docker way" to develop and deploy solutions that we think is very promising.

ZPM bonus is to support the Package manager way to deploy applications built with ObjectScript.

Unit Testing is just helpful and I hope it's clear why we support it.

Evgeny Shvarov · Oct 9, 2020 go to post

So I mean - please show how to run qewd-conduit with iris on docker and the bonus is yours!

Evgeny Shvarov · Oct 9, 2020 go to post

Rob! Correct me if I'm wrong, QEWD-conduit uses InterSystems node.js driver to talk to IRIS, right?  And QEWD-conduit gets Native API bonus for this.

The REST API description requests the usage of InterSystems REST API to have IRIS be a REST API server.

As for the iris docker bonus - we didn't manage yet to run QEWD-conduit with any iris-docker image available according to the QEWD  instruction.

Evgeny Shvarov · Oct 7, 2020 go to post

Here is the set of updated ZPM images with ZPM 0.2.7:

intersystemsdc/iris-community:2020.3.0.221.0-zpm

intersystemsdc/iris-community:2020.2.0.204.0-zpm

intersystemsdc/irishealth-community:2020.3.0.221.0-zpm

intersystemsdc/irishealth-community:2020.2.0.204.0-zpm

And to launch IRIS do:

docker run --rm --name my-iris -d --publish 9091:1972 --publish 9092:52773 intersystemsdc/iris-community:2020.3.0.221.0-zpm

docker run --rm --name my-iris -d --publish 9091:51773 --publish 9092:52773 intersystemsdc/iris-community:2020.2.0.204.0-zpm

docker run --rm --name my-iris -d --publish 9091:1972 --publish 9092:52773 intersystemsdc/irishealth-community:2020.3.0.221.0-zpm

docker run --rm --name my-iris -d --publish 9091:51773 --publish 9092:52773 intersystemsdc/irishealth-community:2020.2.0.204.0-zpm

And for terminal do:

docker exec -it my-iris iris session IRIS

and to start the control panel:

http://localhost:9092/csp/sys/UtilHome.csp

To stop and destroy container do:

docker stop my-iris
Evgeny Shvarov · Oct 6, 2020 go to post

Hi Rob!

Is there a way to run QEWD-Conduit using IRIS Community Edition docker image?

Evgeny Shvarov · Oct 2, 2020 go to post

Another "Realworld" ) That's funny )

Looking forward to seeing how two "realworlds" will compete with each other) 

Evgeny Shvarov · Sep 30, 2020 go to post

Thanks for the reply, Alexey.

my topic is an attempt to find the value in %Status why people use it even for their own methods.

IMHO it steals the option of return values from methods and code looks dirty with “mandatory” $$$TOE or $$$ISERR for every call of the method with %Status