go to post Evgeny Shvarov · Nov 3, 2020 You also can check direct messages here on DC - if people click the I'm Interested button you'll get a direct message.
go to post Evgeny Shvarov · Nov 2, 2020 I think maven is great, looking forward to hearing the news from @Bob Kuszewski
go to post Evgeny Shvarov · Nov 1, 2020 If we host it in the repository until it'd be published on maven, will it solve the issue temporarily? Like here.
go to post Evgeny Shvarov · Oct 29, 2020 We added an IRIS Interoperability Template with a very simple (the simplest probably) but working template of an IRIS Interop production
go to post Evgeny Shvarov · Oct 28, 2020 Also, check my session Creating InterSystems IRIS Analytics Solutions Using Docker & VSCode The related code could be found here on Github.
go to post Evgeny Shvarov · Oct 27, 2020 Sure. PEX demo is included in examples list, thanks @Eduard Lebedyuk
go to post Evgeny Shvarov · Oct 19, 2020 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
go to post Evgeny Shvarov · Oct 14, 2020 While we are building a maven distribution channel the latest IRIS JDBC driver could be downloaded from here
go to post Evgeny Shvarov · Oct 10, 2020 If you are on VSCode try SQL Tools InterSystems addon - it has schema code completion. Is this what you are looking for?
go to post Evgeny Shvarov · Oct 9, 2020 You can take any frontend framework you like: vue.js, React JS, Angular, and many, many more.
go to post Evgeny Shvarov · Oct 9, 2020 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.
go to post Evgeny Shvarov · Oct 9, 2020 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.
go to post Evgeny Shvarov · Oct 9, 2020 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.
go to post Evgeny Shvarov · Oct 9, 2020 So I mean - please show how to run qewd-conduit with iris on docker and the bonus is yours!
go to post Evgeny Shvarov · Oct 9, 2020 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.
