I'll take a look, thank you

I recorded a video to demo that.

Hi @John Murray !

Yes, it just works, thanks to @Timothy Leavitt and his team.

The only thing you need is to make sure that your dev module is described via IPM, and install and setup git-source-control.

Here is an example template for interoperability production that demonstrates the feature. 

And here is the only setup line that is needed after git-source-control is installed via IPM:
 

 zpm "install git-source-control"
    do ##class(%Studio.SourceControl.Interface).SourceControlClassSet("SourceControl.Git.Extension")

@Brett Saviano , maybe I'm mixing something up, but I'm just trying to provide you feedback, that developers that follow the client-side paradigm (actually the majority of existing developers to my knowledge) should still have any option to edit BPL/DTL and DFI and today the way is via server-side UI tools, and of course, they would expect changes reflected in their client git setup, which git-source-control wonderfully does.

Thanks, @John Murray !

I made it work by manually filing the server in a docker container.

The IPM browser works nicely! 

And it beautifully displays what is installed in the namespace.

But I wasn't able to install any app, e.g. tried with Webterminal:

1. Yes, but it can add some automation, as for docker-way port can be a random everytime, so this mean manual setup every build. Which is easy to setup, but every time.

2. Yes, UI Integration. And, if we are talking about client-side editing it is possible to edit those files manually (they are just XML files) of course. But ideally, the developer could call a UI in IRIS to edit the file from within a file, and the changes be saved into this file after editing in the IRIS UI app.

3. What exactly is "incorrect"? ) git-source-control perfectly works as a tool to deliver changes made in IRIS developer UI tools into client-side files. Well, you can say that it is server-side editing, and I agree, as every IRIS-driven developer UI tool is on the IRIS side, meaning server-side in this case. But still, it works perfectly and doesn't demand developers to change their client-side approach to a server-side in this case.

It is possible to deploy frontend/fullstack apps via IPM. Take a look e.g. this or this one.

There is also a helper package for js-based frontend by @Timothy Leavitt, which suggests yet another approach.

So: for everyone who tries it via IPM - works ONLY if installed in %SYS.

Otherwise it installs itself but doesn't work silently.

Is it embedded python or iris python native? (I always mess with them). If the first, try the following for the system:

; enabling callin for Embedded Python

do ##class(Security.Services).Get("%Service_CallIn",.prop)

set prop("Enabled")=1

set prop("AutheEnabled")=48

do ##class(Security.Services).Modify("%Service_CallIn",.prop)

Thanks for the great feedback, @Sean Connelly ! Currently, DC AI is focused on DC knowledge only, which is limited, of course. Great idea about expanding the DC AI knowledge base with ObjectScript basics - we'll consider that in future releases.

That'd be great!

Thank you,, @Henrique Dias !

Thank you, @José Pereira ! Glad you liked it! You did a great solution, like it very much!