BTW, there is a very good one-liner to install ZPM, cortesy of @Guillaume Rongier:

set $namespace="%SYS", name="DefaultSSL" do:'##class(Security.SSLConfigs).Exists(name) ##class(Security.SSLConfigs).Create(name) set url="https://pm.community.intersystems.com/packages/zpm/latest/installer" Do ##class(%Net.URLParser).Parse(url,.comp) set ht = ##class(%Net.HttpRequest).%New(), ht.Server = comp("host"), ht.Port = 443, ht.Https=1, ht.SSLConfiguration=name, st=ht.Get(comp("path")) if 'st { w $System.Status.GetErrorText(st) q } set xml=##class(%File).TempFilename("xml"), tFile = ##class(%Stream.FileBinary).%New(), tFile.Filename = xml do tFile.CopyFromAndSave(ht.HttpResponse.Data) do ht.%Close(), $system.OBJ.Load(xml,"ck") do ##class(%File).Delete(xml)

Now this list could be expanded by Tableau, PowerBI and Adaptive Analytics (AtScale).

Included it into csvgen module.

to export SQL to CSV you can do the following:

USER>set query="select * from your.classname"
USER>w ##class(community.csvgen).SQLToCSV(";",1,"/folder/file.csv",query)

Hi @Guillaume Rongier !

I tried to use pip3 in the app and failed. I see it is being installed during the image build, but cannot run it later. What I'm doing wrong?

And images with ZPM package manager 0.3.2 are available accordingly:

intersystemsdc/iris-community:2021.2.0.651.0-zpm
intersystemsdc/iris-ml-community:2021.2.0.651.0-zpm
intersystemsdc/irishealth-community:2021.2.0.651.0-zpm 
intersystemsdc/irishealth-ml-community:2021.2.0.651.0-zpm  
intersystemsdc/iris-community:2021.1.0.215.3-zpm
intersystemsdc/irishealth-community:2021.1.0.215.3-zpm
intersystemsdc/irishealth-ml-community:2021.1.0.215.3-zpm
intersystemsdc/irishealth-community:2021.1.0.215.3-zpm

And to launch IRIS do:

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

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

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

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

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

docker run --rm --name my-iris -d --publish 9091:1972 --publish 9092:52773 intersystemsdc/irishealth-community:2021.2.0.651.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

And the FROM clause in dockerfile can look like:

FROM intersystemsdc/iris-community:2021.2.0.651.0-zpm

Or to take the latest image:

FROM intersystemsdc/iris-community

Thank you, Robert! What you did and keep doing for the community is priceless! We are very lucky to have you! Thank you so much!

Well done, @Yuri Marx! Thank you! Hope you'll beat your record in 2022! ;) 

Honestly have no idea ) It's was just thought between NY salads eating) But I bet @Robert C. Cemper or @Dmitry Maslennikov could suggest something. I bet Terminal saves aliases in some global that could be investigated. It's a hack of course thus not recommended officially until we document the global.

If you use Docker for development with IRIS this could be easier. E.g. we could run the terminal program(what is it BTW?) during the iris.script phase and setup aliases of taste.

This was a wonderful year - and mostly because of you, InterSystems Developer Community members!

Thank you! Looking forward to seeing how will be 2022!

Wow, @Yuri Marx!

Thanks for the highlights!