multi-user: provide example

[jourdain]

No description provided.

[jourdain]

@SergeyYakubov

[gecage952]

Nice! This works well for me. The only comment I have is that it seems to run at localhost:8080 instead of localhost:8080/app even after setting EP_PATH.

[jourdain]

Indeed but I though those path will be managed outside of the container in a gateway or something.

Why do you need to have a specific path within that docker image? Also does that need to be a runtime or build time option for within docker handling?

[gecage952]

@SergeyYakubov could correct me if I'm wrong, but because we're integrating these apps as tools into Galaxy (workflow management platform we're using) these apps get assigned paths dynamically. Like a user could potentially click and launch the tool (or multiple), and then Galaxy will start the app, assign it a path (partially using EP_PATH, etc. The ngnix config in the repo kinda illustrates what I'm talking about.

[jourdain]

I get the dynamic part which means it is really at runtime and not build time.
But I guess my next question, does the service needs to maintain internally the path assigned on the fly by galaxy or the dynamic infrastructure of galaxy allow to rewrite URL and map them to the root of a running service?

[gecage952]

Ah, I get what you're saying.Yeah, it's probably not an issue, as I believe we actually can just do this via Galaxy. I'm fine with merging this if @SergeyYakubov also approves.

[jourdain]

I'm currently working on enabling that base path in our docker image. So worst case scenario, you will have that available if need be.

[SergeyYakubov]

It depends on the app and how it is implemented. Galaxy can redirect calvera.ornl.gov/app/xxx/ to somehost/xxx. But if the app is unaware of /app and wants to route to /yyy instead of /app/yyy, we'll have a problem. Which might not be the case with Trame, I'm not sure here.

[jourdain]

The app is aware internally and, therefore, can adjust any URL call if need be.

[gecage952]

So, I tried integrating your branch with this repository's dev branch, and I was running into issues getting it working. Since the dev branch is where all of the actual development is happening, can you create an mr to that branch instead and see if it works there (from docker)?

[jourdain]

Ok I'll start a new branch from dev