Was able to install with Brew:

$ brew install caretdev/tap/irissqlcli

AEMBP14ESHVAROV:~ eshvarov$ irissqlcli -h localhost -p 1972 -u _SYSTEM -W

Password for _SYSTEM: 

Server:  InterSystems IRIS Version 2022.2.0.368 xDBC Protocol Version 65

Version: 0.4.0

[SQL]_SYSTEM@localhost:USER> 

select 1

+-----------+

| HostVar_1 |

+-----------+

| 1         |

+-----------+

1 row in set

Time: 0.044s

Amazing. 

Thank you @Dmitry Maslennikov 

You can use InterSystems Package Manager(IPM) to list all the members of production and distribute it to another machine (e.g. your client) via the IPM registry, or using zpmhub.

E.g. you can install several EnsDemo productions as one package:

USER>zpm "install irishealth-ensdemo"

Or recently I published an example of a very simple CSV data transformation production that you can install as one line:

USER>zpm "install esh-i14y-csv"

And here is how all the modules of production depicted in a module.xml.

Hi @王喆 👀!

Message key query has the online demo bonus in place.

But on the IPM(ZPM) - you need to publish the app IPM module to make it available. See the documentation:

 https://docs.openexchange.intersystems.com/solutions/submit/#package-man...
 

Also, please follow the naming convention for ObjectScript classes and IPM modules.

Turned out, the following call should be executed to let source control start working:

do ##class(%Studio.SourceControl.Interface).SourceControlClassSet("SourceControl.Git.Extension")

Check Interoperability template to discover Git integration for Interoperability UI components. Production, Business Rules (old UI), Business Process and Data Transformations are supported.

Things to know:

1. Make sure the settings export changes in the folder you want, can be adjusted in the git-control UI.

2. Every Interoperability component should be first added to source control manually (in the git-control UI, add button).

3. Make sure you export the git-control settings too! They are in ^SYS global. @Timothy Leavitt , we also need source control for git-control settings ;) (Could be a ^git-control global name ?)

For now I use the following line to export it in a proper format and in a proper place, which I still call in a Terminal:

do $System.OBJ.Export("SYS*.GBL","/irisdev/app/src/gbl/SYS.xml",,.errors)

And I import it with the following setting in module.xml:

<Resource Name="SYS.GBL"/>,

a full module.xml example

4. @Timothy Leavitt , Would be great to have the UI to have the editable list of all the source-controlled elements. E.g. to easily transfer ^SYS global between projects. As the majority of settings for docker-enabled setups are the same, but the list of source-control elements is different.

@Guillaume Rongier , have a look! )

I think we are heading the NPM route. Quantity does not mean better. Quality does. We are all strong developers and individuals, and we all want to make a difference and contribute. We all also want that contest prize, to be honest. The contest prize I think pushes the people, which is good, but maybe contributes towards the single contributor packages. I am not saying the contests should stop, but maybe when doing something for a contest, try and do it and take part without making a new package. Chat with the Repo owner - I am sure the owner will not mind if you improve on their repo and get the prize.

Regarding it. First of all, thank you for the feedback. This is very important and we are looking for such a feedback all the time.

Yes, we have 700 apps, and 4 years ago we had zero and contests helped to have some variety.

Also, I hope every member of this developer community could participate in a contest with the new app, as it as we think gives a habit to stand-out from your own dev-bubble and consider docker, ipm, online demos, unit-testing and sometimes provide a feedback!

But on contrary we encourage very much re-applying with already created apps and we see several improved apps even in the current contest.