Thank you!

Thank you, @Irène Mykhailova ! I can even feel the summit's atmosphere with your report! Wish I were there with all the team!

Package Manager is going to be a part of a product in near future, but right now it is not a part and can be installed with the following command:

s r=##class(%Net.HttpRequest).%New(),r.Server="pm.community.intersystems.com",r.SSLConfiguration="ISC.FeatureTracker.SSL.Config" d r.Get("/packages/zpm/latest/installer"),$system.OBJ.LoadStream(r.HttpResponse.Data,"c")

Caution!  This is for IRIS only.

The package manager.

It has documentation, a bunch of videos, and there is a tag here.

I'm not answering your question, but just as a side note - with using Docker as a dev environment you don't bother with installing of Ensemble or IRIS at all. You can switch IRIS version at any moment if something went wrong or you need a fresher version.

In case of IRIS Community Edition just download the newest desktop version or pull the latest docker image - both will contain the refreshed license

Hi @Guillaume Rongier !

Well explained. I just hope the UI be more intuitive - this pays a lot in the future for the better adoption of the tool.

I understand that there are not many letters in the alphabet and it can go to the end quickly. In this case I'd keep with what you think on one-letters and also introduce synonyms of fulltext with double --.e.g.

--import for import,

--export for export and 

--status for status.

This could help with readability in long scripts with cli or with documentation.

Great stuff, @Guillaume Rongier !

A few questions: 

iop -x 

-x is for status? Why not -s?

Also, 

iop -e PEX.Production

is for export? Can then this export be imported?

Tried with the project where I have ObjectScript Unittests. I call them manually with IPM and automatically with github workflow.

Testing manager is installed, I'm on a class with unit test.

Not sure though how it works?

If I can guess you need export several classes/routines/macro in one file e.g. to deploy to another server.

I'd recommend to use InterSystems Package Manager for it

Why FARGATE_SPOT is important?

Learn more about Github Container Registry - a part of Github Packages service. 

And thanks again! I went through all the steps and it's working fine!

BTW, @Yuri Marx , the part for creating registry, building and pushing docker image into it could be omitted by using Github Registry.

Github provides a free of charge registry for public images. Everyone can create a public image automatically just by adding one workflow file into the repository, .e.g. this one. And this action builds and publishes x86 image to Github Registry in a form: ghcr.io/account_name/repo_name:tag. for iris-rest-api-template repository the image is:

ghcr.io/intersystems-community/iris-rest-api-template:latest

So with AWS we can start from cluster creation and use this image in a task.

Tested it now - works fine!

Also, can I have a storage for IRIS database that will not be deleted with every container restart?

Also, is it possible to start provisioning automatically with every commit to a master branch of a github repo?

Thanks @Yuri Marx! How to add a TLS and domain name? 

Is there a way to get a terminal access to the server?

Useful article, @Hiroshi Sato san! For source control I recommend $system.OBJ.ExportUDL() method to export in CLS, MAC, INC formats. $system.OBJ.Load() and $system.OBJ.LoadDir() methods support both XML and UDL formats

Hi @Larry Overkamp !

You can use $system.OBJ.ExportUDL() to export in CLS or MAC or INC.

and $System.OBJ.Load or $system.OBJ.LoadDir() to import CLS or XML or MAC.

As for transferring code between systems I'd recommend to maintain code in repositories (e.g. git) and deploy code via InterSystems Package Manager.

Hi @David Hockenbroch! There is a set of articles related to InterSystems reports - maybe they talk about API also. 

Ah, great. I didn't see the info that odd-numbered are preview releases! Looking forward, thanks @Raj Singh !