Accessing an external URL within a paraview app

[smkacur]

Hi Seb,

I have a trame application that visualizes some VTKs using paraview and also uses plotly to visualize some weather data. I would like to hook the application into an API in order to retrieve the weather data in near real-time.

I have a module that I use to call the api and then I import those functions into my trame application. I tested a version of the plotly app by itself to confirm that the api calls function properly and that the data plots. However, when I try to run those same calls within the paraveiw app they fail because pvpython doesn't come with SSL and the API is https. I am reaching out as I would like your advice on how to move forward.

Would it make more sense to install OpenSSL when building the image? Or should I use wslink to to make the external API available to my application without requiring SSL? I do not know much about web sockets so if the latter solution makes more sense then any pointing in the right direction would be extremely helpful.

I saw this issue here: #334 which aims to serve the trame app over https so I guess making the url available to my application would follow similar logic?

Some additional context: I am not using the cookie-cutter template but I am building the application with the multi-user image and building the server directory with the shell script.

FROM --platform=linux/amd64 kitware/trame:py3.9 as trame

RUN install -d -o trame-user -g trame-user /deploy
RUN apt update -y && apt install -y libosmesa6-dev
ARG PV_URL='https://www.paraview.org/files/v5.11/ParaView-5.11.0-osmesa-MPI-Linux-Python3.9-x86_64.tar.gz'
RUN mkdir -p /opt/paraview && cd /opt/paraview && wget -qO- $PV_URL | tar --strip-components=1 -xzv
ENV TRAME_PARAVIEW=/opt/paraview
ENV TRAME_CLIENT_TYPE=vue3

COPY --chown=trame-user:trame-user . /deploy
RUN export TRAME_BUILD_ONLY=1 && /opt/trame/entrypoint.sh build

[jourdain]

I guess, here are the options:

1. Build paraview with OpenSSL
2. Use conda and install ParaView (but I don't think that will work in docker because of the rendering backend)
3. Use spack to build ParaView EGL within docker and SSL

My pick would be to either trigger a build with SSL (1) in our superbuild or use spack within docker (3).