Community version of IRIS and IRIS for Health are available on download.intersystems.com

Community docker versions of IRIS and IRIS for health are available on InterSystems store at dockerhub.com with the following tags:

docker pull store/intersystems/iris-community:2019.4.0.379.0

docker pull store/intersystems/irishealth-community:2019.4.0.379.0

Enterprise versions of IRIS and Caché are available for download at wrc.intersystems.com .

Also InterSystems IRIS Enterprise and Community Edition are avaialble via InterSystems cloud offerings on AWS, GCP and Azure.

HTH
 

I'll participate in the meetup with the session:

📌 11:45 – 12:15     
Resources and Services for InterSystems Developers. ObjectScript Package Manager Introduction

Takeaway: Attendees will learn about  Developers Community, Open Exchange and other Resources and Services available for developers on InterSystems data platforms and will know about InterSystems Package Manager and how it can help in InterSystems IRIS solutions development
 

Come join InterSystems Developers Meetup in Israel!
 

Updated the Installer.cls file - now you can set up the namespace and path in variables "Namespace" and "app" respectfully at the top of  Installer.cls.

  <Default Name="Namespace" Value="IRISAPP"/>
  <Default Name="app" Value="irisapp" />
 

This is convenient if you need to install the app to the namespace with your name.

Notice, that if you want instantly edit and compile the code of your project with VSCode don't forget to change the Namespace parameter in settings.json too.

Hi Rubens! Thanks for the valuable input.

Yes, freedom is a great thing as soon as nobody harms you upon freedom concepts. What I mean everybody should enjoy the freedom and that's why we perhaps need some community rules to avoid chaos. 

E.g. what if some developer will introduce another module Frontier then Rubens Silva's Frontier?  And if I want these modules to run both in one namespace? 

It's not rocket science, people already have invented naming conventions that's what I'm going to talk and agree about.

- The notes/documentation say that code will be loaded into USER namespace, however it's actually being loaded into IRISAPP (as configured in docckerfiles).  

Because I made an update to the code recently) And not to the documentation) PR is welcome, or I'll change it by myself soon. Or add an issue!

- The jason.config is pointing to USER namespace so any new files and changes to existing will be actually loaded into USER instead of IRISAPP

Yes, it's a bug from previous version. Need to be fixed, thanks!

- The webapp (irisweb) is missing a config for the directory where to store files. I fixed this by modifying the app in management portal. Need to address the installation file/dockerfile

Cool!

Do you want to make a PR?

- Haven't been able to make CSPs flow to the container the same as classes. I'm sure I'm missing something but haven't figured out what yet. Any tips? Maybe I'm placing files in the wrong location? Right now I created a csp/irisweb folder under src folder.  

You need to COPY this files from /csp in sources to /usr/irissys/mgr/csp/yourwebapp  in Dockerfile