and code quality will struggle with it and dislike it
because you use name in write, but you don't set it explicitly
but don't care much about:
it doesn't understand %-variables and global variable scopes
and $$$macros with code inside, and ... and ... and
to get control over your situation you have 2 key methods:
So you have to check if your user has exhausted its available connections and block him.
It's anyhow quite interesting how these users are able to trigger so many connections.
This is intentional behavior.
If the routine you changed calls some subroutine it is kept "on the stack"
This is a requirement to have a save return and continuation after the call.
The new version only becomes active after you have left the previous one by QUIT or RETURN.
simpler: if it is gone from the return path.
I share your suggestion!
When I started with Docker I was highly skeptical after many years with VMware starting before their first release.
It was a hard exercise and I took quite a while digging through docs and helps.
My main problem was that everything was so generic and not at all specific to IRIS (or Caché).
Meanwhile, it became so common to me that I stopped running reviews on packages without docker.
Docker allowed me to have a "clean desk" after testing.
In addition. I saw through this activity so many valid variations that
I doubt to decide how to start and where.
On the other hand, I see in OEX ~450 tested and working examples (a dozen PR still pending)
Following these examples and trying to understand what will be achieved
could be good food for training designers.
You may have only 1 command: in each build
the 2nd overwrites the first
iris:
image: intersystemsdc/iris-community:latest
command: --check-caps false
container_name: tls-ssl-iris
networks:
app_net:
ipv4_address: 172.16.238.20
volumes:
- ./iris-config-files:/opt/config-files
# Mount certificates files.
- ./certificates/CA_Server.cer:/usr/irissys/mgr/CA_Server.cer
- ./certificates/iris_server.cer:/usr/irissys/mgr/iris_server.cer
- ./certificates/iris_server.key:/usr/irissys/mgr/iris_server.key
hostname: iris
# Load the IRIS configuration file ./iris-config-files/iris-config.json
command: ["-a","sh /opt/config-files/configureIris.sh"]
this worked as multi-line
command:
- -a
- sh /opt/config-files/configureIris.sh
- --check-caps false
BUT
command: ["-a","sh /opt/config-files/configureIris.sh","--check-caps false"]
works as well
nothing prevents you to load this script at runtime from server.
<script src="myscripts.js"></script>
from w3schools.com https://www.w3schools.com/tags/att_script_src.asp
So you are outside your Caché
I do the same exercise in my package GlobalToJSON-ePython-pure
it should be basically sufficient to replace the JSON packing + writing by print(...)
see >>> def node(nd,nxt,fil):
in my various examples I took these strategies:
to my experience, your 'KeyError' indicates that you try to get a value
from a non-existing global or subscript. in COS it would be <UNDEF>
in my package GlobalToJSON-ePython-pure
I developed this workaround:
#; simulate $data() for existence and content
def Ddata(gref):
val = None
_d = 11
#; check for subscripts
o=gref.order([])
if o == None:
_d -= 10
try:
val=gref.get([])
except KeyError:
#; no value @ top node
_d -= 1
return [_d,val] NIce you share a picture of a PDP11 !
a few of my heroes:
---
I know also some handicapped developers.
BUT: I find it highly insensitive and inadequate to drop their names in this forum
Any sport that requires mental concentration. eg. mountain climbing,
And I mean REAL climbing, not just moving your body somehow across nature.
With 2 very successful sons in software, internet, and project engineering (49yrs. + 36yrs.)
I have a valid benchmark for my strategy.
A real software developer doesn't care about the hardware or operating system.
Specific hardware is a subject for gamers.
I use and just verifiied
iris.cls(__name__).SetupGame()
I enjoy to solve what was declared to be IMPOSSIBLE before.
I dislike it if it turns out that issue was just a fake and nobody cares about my creations.
--progress plain
This is essential information.
Without it the building log just runs though with no chance for a rollback
and iris.script allows a lot of temporary debugging info.
my PR contains an update on docker-compose.yml
and a bash script startflask.shall available here https://github.com/rcemper/iris-python-flask-api-template
Sep.23 all merged
The actual GTY is containers.intersystems.com/intersystems/webgateway:2022.1.0.209.0
And there is no :latest defined
You're welcome. Those things keep my mind in speed. 
DONE!
I found my solution and placed it in a PullRequest.
it was slightly more than just a missing port.
You may use input redirection as you find it in almost all Dockerfile installations:
RUN iris start IRIS \
&& iris session IRIS < iris.script \
&& iris stop IRIS quietly
and iris.script (as example)
zn "%SYS"
Do ##class(Security.Users).UnExpireUserPasswords("*")
zn "USER"
As Issues are disabled in the GitHub Repo I place my issue here.
Congratulations to all winners!
Not sure if I can make the date.
Anyhow using Studio since its first days in Caché 5.0 for 20+ years almost daily
and still firmly tied to Windows I just have no need for change.
And I use my experience with all tricks and shorthands burned deep in my mind.
It's just Dino's behavior as a veteran that started with X ^% in terminal
nice
but how does ERLANG relate to IRIS or Caché ?