go to post John McBride · Mar 4 Hmm, so sounds like is pretty early on for the node support? Kinda hinders anyone trying to build a UI around the IRIS Apis since they are not really exposed or generally available to call via HTTP. I know these library wrap alot of internal structure to present it in a way that the library understands but still hinders anyone wanting to build a webapp around IRIS (sepcifically not something hosted on IRIS).
go to post John McBride · Feb 21 @Summer Myerson @Stefan Wittmann Any update of the packages in nuget?
go to post John McBride · Feb 19 So here is answer is anybody is interested and running Iris for Health in a container and front ended by the nginx webgateway container. First - What ever url name you use in the web application configuration you will need to add to the nginx config file. See below Next - when access the url be sure to add the trailing slash (/) otherwise you will get a "url not found on this server message. I'm not sure why this happens as both URLs *should* work? Hope this helps. Example:URL Name: /csp/flask You will need to add it to the CSP.conf file for the nginx config like the following location /csp/flask { CSP ON; CSPNSD_pass 127.0.0.1:7038; CSPNSD_response_headers_maxsize 8k; CSPNSD_connect_timeout 300s; CSPNSD_send_timeout 300s; CSPNSD_read_timeout 300s; }
go to post John McBride · Feb 6 The problem is that when you try to install the flask app you get the screenshot (1st) that says it cannot find a WSGI runtime (like flask or django). The answer is, for a container, you need to install the flask runtime in the OS level not the virtual environment level. Example would be like this (In the Dockerfile) to install the flask runtime during a container build. This will install the runtime correctly and you will not get the WSGI message when trying to create an application. RUN apt install -y python3-flaskRUN apt install -y python3-django
go to post John McBride · Nov 19, 2024 @Summer Myerson Thanks for the info. Does the container versions of iris also contain those? I looked at the durable volume and didnt see them.
go to post John McBride · Nov 7, 2024 Even during building? Normally you would specify a key during the start of a container via the --key parameter. How would you do this with a docker build command? Copy the key into the container?
go to post John McBride · Nov 6, 2024 So, If i want to build a container (not the community version) I would need a license? is that what I'm reading from your comment?
go to post John McBride · Aug 28, 2024 Thanks @Alexander Koblov Would this also apply to the python library as it supports the same IRISReference?
go to post John McBride · Jul 15, 2024 Looks interesting, but that project still needs to be installed on the iris system. IMO I was something that is independent of the IRIS platform and is tightly integrated into a development environment. Which is why I built it into VSCode. I don't want to have to install and entire app on infrastructure to make it work. If that solution works for you workflow, its a great option as well Just my .02
go to post John McBride · Nov 26, 2023 yeah, it'd be interesting to see if Intersystems would be interested in building an opentelemetry SDK for object script. Maybe there's a way to use .NET or python and the external language server as a proxy to call from object script...
go to post John McBride · Nov 26, 2023 I believe OpenTelemetry has support for multiple features, metric, tracing and logs (atleast from my understanding)
go to post John McBride · Apr 14, 2023 Hi Patrick - Thanks for the response. I am currently just one container, not really seperating out the webgateway just yet. Right now i'm just using the priate web server contained within the iris4health container. With that being said, do I still need to add the ssl/tls items into the webgateway config. I thought that was just to secure the communication between the webgateway and the iris server?
