Ben Spead · Feb 3, 2022 go to post

Thank you @Craig Regester  for the response.  Looking up that file in the docs (https://docs.intersystems.com/iris20201/csp/docbook/DocBook.UI.Page.cls…
) it tells me that "For security reasons, the parameters.isc file is accessible only by the root user."  I am pretty sure there is a way to tell what it is currently running as without needing that level of access.  But it is good to know about this in the cases where root access is an option

Ben Spead · Feb 3, 2022 go to post

Is there a single development server which all developers connect to?  If you are not able to have a fully isolated development environment for each developer then you will end up getting frustrated trying to use client-side source control.

You might want to consider the new server-side Git source control hooks which were recently launched:

https://community.intersystems.com/post/git-shared-development-environm…

This won't solve your issue of working while not on VPN, but it will allow multiple developers to work against the same instance without stepping on each others' toes.  

Ben Spead · Jan 28, 2022 go to post

@Don Martin - It looks like there a typo:

its "irishealth-ml-community", not "irishealth-community-ml"

Try

podman pull containers.intersystems.com/intersystems/irishealth-ml-community:2021.1.0.215.3

(credit to John Martin in ISC RelEng)
 

Ben Spead · Jan 25, 2022 go to post

nice article, thank you for sharing.

Small note - Download is misspelled in the first step of your directions

Ben Spead · Jan 14, 2022 go to post

@José Pereira , thank you for sharing!!  Please note that you have a small typo in your title - pratical > practical (no worries, if I wrote a D.C. article in Spanish you would lose count of all of the typo's ;) ).  

Ben Spead · Jan 14, 2022 go to post

Quick note that the Announcement has been updated to include links to the specific course PDFs as well as links to the online version of those courses where one is available.

We are still looking for some more people from our larger implementation community to take part in this Beta Test - please sign up today if you haven't already done so! (and THANK YOU in advance :) )

Ben Spead · Jan 12, 2022 go to post

Nice job everyone - congratulations and thank you for your contributions!! 

Ben Spead · Jan 11, 2022 go to post

You should still be able to get into the instance while it has an expired key ... you just can't make multiple simultaneous connections to it.  You can also grab the iris.dat files from the file system (which actually stores the globals) and then mount them to another instance.  Or you can just upgrade that instance to a new version of the Community Edition (which is likely the easiest approach)

Ben Spead · Jan 5, 2022 go to post

Rob ... this is incredibly rich - thank you for taking the time to write all of this up!!

Ben Spead · Dec 17, 2021 go to post

It should be safe to edit manually as long as you are not changing the piece numbers or changing the order around.  Simply changing the property name within  <Value>...</Value> of the storage definition should be fine if it is no longer used at all.  In our case, we have had instances in the past where we needed to change a property name and rather than creating a new property and migrating the data it proved to be safe and much more efficient to change the property name in both the property definition and the storage definition (as well as all of the places in the source code which refer to it).  The nice thing about this approach is that we've been able to simply do a Find/Replace in all of the source code and carefully review the diffs before submitting.  

If others are aware of gotcha's when changing the storage definition Value, I would be interested in hearing them.