How to use AfterInstallMessage ?

Thanks, @Jane Yan for sharing! Looks like a very timely and in-demand solution! Good luck with going to the market!

Proud of our Dev Ecosystem Team! Thanks, @Anastasia Dyubaylo  for sharing! My favorites are Random Coffee, New About page, and Key Questions! And of course the Memes! Who says that summer is a quiet time - not in the InterSystems Developer Community! 

Perforce is nothing to do with the case, but I agree with @Dmitry Maslennikov - you shouldn’t deploy classes without storage, it can cause unpredictable and severe errors in case of data structure changes (e.g. if you rename/delete the property).

Hi @Patty Aguirre-Romero !

You may want to have a look at the EnsDemoEnsDemo project on OEX. It has a set of productions with BPL I believe. 

can be installed in any IRIS with ZPM:

USER>zpm "install irishealth-ensdemo"
 

I second with @Dmitry Maslennikov  - the easiest and handiest way to stay up-to-date with current versions of InterSystems Docker images is to use Docker Desktop and set up an InterSystems extension.

For those who will participate: please prepare your tips&tricks for:

1. Development

2. Debugging

3. Working with version control

4. Hidden gems

5. Final arguments!

There will be an option to demo your skills and approaches!

I'll be there!

Thanks, @Robert Cemper ! I encourage Docker usage too! It's not only easy to try and thus easier to get a review, but it's also easy for other developers to contribute to your one. Here is the basic template to start your docker development with IRIS.

Hi @José Pereira ! Don't you plan to contribute an example on OEX?

Hi @Lucas Enard! Thanks for such a great contribution to the community!

I have a question: where can I obtain an API key for GPT2 to run the test:

{
    "api_url":"https://api-inference.huggingface.co/models/gpt2",
    "payload":"Can you please let us know more details about your ",
    "api_key":"----------------------"
}

If you want to add a quality check to your applications, just add this file to the GitHub repository. This will perform a check automatically with every commit.

Very useful feature! Thanks, @Elena E !

And here is the link with which you can see the applications that accomplish the test.

I guess you know more about it.

I’d also ping @Dmitry Maslennikov 
as he tried to make a ZPM package for the whole documentation.

I see that the documentation pages are IRIS CSP classes. So I guess it could work if installed in IRIS. I guess also there is a set of static files (FILECOPY could help).

IMHO, the reasonable approach to have a separate repo ensdemo-doc and a separate module the, which will be a dependent module to irishealth-ensdemo

So people could contribute to documentation independently and update it independently too.