This is how I have been setting up IRIS instance local filesystem registries. I'm still using an old 0.9.1 version so your version might behave differently.

The repository location is recorded by environment variable IPM_LOCAL_REGISTRY.

In ObjectScript shell %SYS namespace:

// install ipm
do $system.OBJ.Load("/path/to/zpm-0.9.1.xml","ck",.errorlog)
// setup local filesystem ipm registry
zwrite ##class(%IPM.Main).Shell("repo -name REPONAME -filesystem -depth 2 -path ${IPM_LOCAL_REGISTRY}")

A (minimized) bash script used to install module tarballs:

#!/bin/bash

declare -r tarball=${1}

declare -r workdir=$(mktemp --directory --tmpdir=/tmp ipm-module.XXXXXX)
trap "rm -rf ${workdir}" EXIT

declare -r manifest=${workdir}/module.xml

tar zxf ${tarball} -C ${workdir}

declare -r name=$(perl -ne 'if (m/<Name>(.*?)<\/Name>/) { print "$1"; last; }' ${manifest})
declare -r version=$(perl -ne 'if (m/<Version>(.*?)<\/Version>/) { print "$1"; last; }' ${manifest})

declare -r module_dir=${IPM_LOCAL_REGISTRY}/${name}/${version}

if [[ -d ${module_dir} ]]; then
  echo "Module ${name} version ${version} is already in the local registry"
  exit 0
fi

mkdir -p ${module_dir}
cp -r ${workdir}/* ${module_dir}

It will untar the tarball, figure out the module name and version from the manifest file and copy the sources to correctly named directory.

I also have other scripts that will fetch the tarballs from the actual artifact repository where the module tarballs are stored.

The last test (or assert) in TestLowerCase() is faulty (testing an empty string).

##class(Ens.Director).GetProductionStatus() will tell you if the production state is running/stopped/suspended/troubled.

Documentation:

https://docs.intersystems.com/iris20241/csp/documatic/%25CSP.Documatic…

Just nitpicking but I think it's 2022.1.7.1116.1, not 116.

I guess the 2025 answer is to look at Python solution(s) which are likely many. A quick internet search suggests e.g. https://pypi.org/project/jsondiff/ that seems to be a reasonable complete, recent and popular.

Unfortunately I'm not yet arrived to IRIS Python-land, hence I had to come up yet another partial solution that fits to my current use case:

https://github.com/janihur/objectscript-ex/blob/main/src/OSEX.Json.Comp…

How to take control of your own code snippets:

The "old school" way: keep a "tidy" public or private repository from where you can easily import the code into any namespace with $system.OBJ.ImportDir

The "new school" way: organize the code into a public or private IPM module (or modules). In case of public code host the module(s) in https://openexchange.intersystems.com/?zpm=1 Remember to be explicit about the license!

Select top level package name (try to follow the de-facto naming rules) and organize the code there as you see best (use sub packages and classes).

I don't know about public collections of functions but browse and follow-up the https://openexchange.intersystems.com/

If you update from IPM 0.7.x to 0.9.0 [...]

I have no idea how one could update IPM and I don't see updating mentioned anywhere in the documentation. I created https://github.com/intersystems/ipm/issues/673 with a bit more background. Let's continue discussion there.

v0.9.1 has been out for some time now!

https://github.com/intersystems/ipm/releases/tag/v0.9.1

I'm definitely and permanently fallen behind and used already most of my annual skill+time puzzle quota. So I'm not expecting to solve more than 7 or 8 first days. However you'll get a small story about my learnings here when I'm done ;)

Any updates when 0.9 will be released?

I'm not sure if there is other options too but how about to convert the dates into strings? In select use to_char() and in insert use to_date():

select
-- date to string with to_char()
to_char(current_date, 'YYYY-MM-DD') as date1,
-- string to date with to_date
to_date('2024-11-14','YYYY-MM-DD') as date2