Multi user support

[JT3DAI]

Hi all,

Please forgive me if this has been asked and answered before but I couldn't find an answer

I have a multi container docker configuration of which trame + paraview is the front end. I use docker compose to launch all the containers. Each of the other docker containers are communicating using http post and get. I used cookie cutter example to help build the trame docker app. It all works and I can login with one user using MSAL and store everything in azure specific to that one user.

But I don't know how to handle multiple users in trame using MSAL. Each user should only see their data and and interactions with a 3D mesh / point cloud should not interfere with another user "session"

So at a high level what is the best way to do this. I see mention of a multi user example using this example but I don't see what it is doing that is different to a normal trame app.

Thanks in advance

[jourdain]

In the default docker setup, each process is ran under trame-user. After that it could be up to your python code in your trame app, to retrieve the proper user and only serve/load the "user data". But without more details on your app design and how you separate your user data, it is hard to provide relevant guidance.

Feel free to reach out to Kitware for professional support.

[JT3DAI]

Hi Seb,

As always appreciate the reply.

So I looked into this more and I better how the scripts work in the docker folder to create the launcher.json + server folder. To date I was not using these scripts as I was using an active development with hot reload but I was missing out on the launcher per tab session that comes with using these scripts which led me to ask the first question. But I see now that this functionality is available which is great.

So my questions is - is it possible to have hot reload in a development environment but also use the launcher feature to create sessions per browser tab? Otherwise development will be very slow?

I can't see an easy way to accomplish this. It looks like i may have to delete the server folder every time I want it to pick up on new changes made in either the python or vue components code in a cookie cutter trame project. I would then have to run the build_image.sh script again. that fine in a production environment but not development

If this is complex I can reach out to them team in France

Thanks in advance

[jourdain]

So my questions is - is it possible to have hot reload in a development environment but also use the launcher feature to create sessions per browser tab? Otherwise development will be very slow?

Yes, you can make sure you add --hot-reload in the args of your cmd in your launcher config. Also, you need the venv to have your code base installed with -e.

For the web part, you will need to re-run trame.tools.www if you must use docker. Otherwise, you can use a local setup of the launcher with direct ws connection rather than relying on apache to deal with the network routing.

[JT3DAI]

Ahh super. Many thanks Seb

One last one

Can I use is it possible to use FROM kitware/trame:py3.10-glvnd as the base image. I need to also have paraview installed in this container but when I do use it can't find wslink in the venv like it can in FROM kitware/trame:py3.9. I'm going around in circles trying to get it to work!!

[jourdain]

Which version of ParaView are you using? The docker python version must match the one from PV.

[JT3DAI]

I am doing this in the dockerfile. but i am flexible on what version if it helps?

# Install ParaView
ARG PV_URL='https://www.paraview.org/files/v5.13/ParaView-5.13.0-egl-MPI-Linux-Python3.10-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

[jourdain]

I'm just guessing here, but I bet you built the server directory with a py3.9 image. So you need to delete that directory and restart the process with 3.10 or simply bundle the 2 steps into 1 docker image like we do in the docker trame examples.

[jourdain]

This is a 3.9 image, so you need to use the same one as the one in your docker definition.

[JT3DAI]

so this is what I do Seb so you might correct me if I'm doing something stupid. I hope I am and you can spot it

1. I create the project with cookie cutter as per the instructions on this page
2. For this test i used the same settings and created the visualis application
3. The dockerfile is left as is and is using FROM kitware/trame:py3.9
4. I then run the script build_imgae.sh in bundles/docker/scripts
5. I then run it with run_image.sh
6. All works fine
7. Then i delete the server directory and change the docker file to FROM kitware/trame:py3.10-glvn
8. Then I repeat steps 4 & 5
9. Then it fails with something going on with not being able to find the packages - wslink is the first one it tries to get but I'm sure it will fail on them all

Could it be a python 3.9 vs 3.10. For example any way it created the venv with 3.9 but then when it installed was using 3.10 or something like this?

[jourdain]

Like I pointed earlier, you need to change that line in the step 4 to use the same image as your runtime.

Basically that build_image.sh file should look like

#!/usr/bin/env bash
CURRENT_DIR=`dirname "$0"`

cd $CURRENT_DIR/..
DEPLOY_DIR="$PWD"
cd ../..
ROOT_DIR="$PWD"

docker run --rm          \
    -e TRAME_CLIENT_TYPE=vue3 \
    -v "$DEPLOY_DIR:/deploy" \
    -v "$ROOT_DIR:/local-app"  \
    kitware/trame:py3.10-glvn build

[JT3DAI]

ahhh i think that is it. I'm off to test properly but I think you solved it. Really appreciate the help!!

So i know. How come we have to state the exact image for 3.10 but we didn't have to for 3.9

In other words how come this works for FROM kitware/trame:py3.9 Do they not have to match? Or is this the default?

#!/usr/bin/env bash
CURRENT_DIR=`dirname "$0"`

cd $CURRENT_DIR/..
DEPLOY_DIR="$PWD"
cd ../..
ROOT_DIR="$PWD"

docker run --rm          \
    -e TRAME_CLIENT_TYPE=vue3 \
    -v "$DEPLOY_DIR:/deploy" \
    -v "$ROOT_DIR:/local-app"  \
    kitware/trame build

[jourdain]

Because kitware/trame is using python 3.9 internally. So building a venv for Python 3.9.

[jourdain]

The idea is to have a "trame" image using the same python as your runtime.

[JT3DAI]

ok I get you.

Again appreciate the help with this. I'll do a bit more testing and then mark as answered