Developer Advocate / Software Engineer / Technology Evangelist
Seasoned pragmatic software engineer and technologist with a passion for all things developer advocacy. Over 20 years experience in building teams, products and communities ranging from tech companies to healthcare with a varying range of technologies from cloud to highly secure On-premises environments.
Thanks, I'll try this when I get a moment
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).
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.