Hi all I am looking into helping the team detach the questdb UI from the database as a container. Whom should I be in touch with?
03/07/2023, 11:54 AM
Hello Shan, this is currently not supported. What is your goal? To run the UI on a different server or disable it entirely?
03/07/2023, 12:13 PM
I went through the UI repo and found that it just might be possible to run questdb's UI as a different container. This might be helpful also to address the problem of serving the ui behind a path e.g.
in the long term
so the database can run headless but you can spin up a container with the UI and connected it accordingly when needed. Also beneficial maybe in the future when the same UI needs to connect to multiple QuestDB instances for troubleshooting or querying
03/07/2023, 12:40 PM
right, if you are keen to experiment then it’s definitely doable. what I meant is that it’s not officially supported.
in theory - the separation should be rather simple: the web console is really a static page and a bunch of REST calls.
if you are willing to explore this a bit more and perhaps document your finding then I am sure there’ll be people who will appreciate this!
03/07/2023, 12:42 PM
I am willing to explore this because I have been playing around with docker for more than 5+ years now and I think it is doable especially for Quest. Is there a subchannel where the UI devs have some talks + discussions?
03/07/2023, 12:43 PM
I don’t think there is a sub channel, but feel free to use #contributors