-
Notifications
You must be signed in to change notification settings - Fork 400
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Need help for deploying Dtale in production #731
Comments
@sourav9599 one thing I can think of would be to override the The way the filtering could work is that when you add a new piece of data to D-Tale within your app you can add the username to the name property and then filter them by any instances with that user's name in the
I'm not really sure how the Docker container approach would work, but if you could come with something using kubernetes that would spin up a D-Tale process on demand for each user and kill it after some period of inactivity then that might solve your problem. That being said, I don't know how this would be accomplished. |
I have it running for my team in a docker swarm with traefik which makes it somewhat doable with sticky sessions and a limit of one user per replica. Only problem is how to properly clear Dtale when a user have left their session unvisited for prolonged time |
@jakob1379 Thanks for the solution, I will definitely look into this!! |
I've created a Flask app with Dtale using build_app from dtale.app, which includes other routes. To isolate Dtale instances for different users from my frontend, I'm using sessions.
ISSUE:
Clicking on the 'instances' button in the Dtale UI allows me to view and delete running instances from different user sessions, which is not ideal. What can I do to prevent this?
According to my research, creating a Docker container is recommended to isolate the backend for each user session. Are there any alternative approaches to address this issue?
The text was updated successfully, but these errors were encountered: