New post
AllAccepted answers
John McBride · May 17

After some more debugging here are my findings. It would be beneficial for a Intersystems person to validate these findings.

It appears that in order to use packages in a Flask App deployed to an Iris docker container, you will need to install the packages at the os level of the container. What does this mean? It looks you have to create a custom container using the docker build process and install the needed packages into the new image container, using the base image of the Iris container.

Can someone comment on if this is the suggested way to install packages that a flask would need into a container iris based environment? Kind of defeats the purpose of have a python venv in the container. If you have to create a new base image everytime someone wants to add a package to the flask app, not very dynamic...

Debugging steps:

a. Tried using the base image and deployed a flask app. Getting error message above.
b. Created custom container via docker build with flask packages installed at the OS level. Ex: RUN apt install -y python3-flask
c. Base flask app worked
d. Tried using packages like flask-session, etc application would crash stating it could not find module.
e. Installed packages using the virtual environment in the container (/dev/python/virtual/%Python Server_3252368016$) by first activation the venv, then running pip install. Verified packages were in the correct location
f. Created new container with docker build and adding the packages install into the OS level. Ex: RUN apt install -y python3-flask-session.
g. Started the new container image, Flask app now works as expected.

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).

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;
}
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-flask
RUN apt install -y python3-django

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

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?