BrandonE
Explore a separate image for lila-ws and using docker compose
Right now lila-ws is fired off as a background process. It could instead be run by a separate Docker image and orchestrated together with lila via docker compose.
I thought more about the potential benefit of doing this, and I landed on "you could see the logs of lila-ws". However, the current implementation writes out the logs to nohup.out in lila-ws directory, so they are already there if you need them. I don't think we need to do anything.
Even though I probably won't do this, it's probably better to do it this way and thus we should leave this open in case someone is interested.
I'm trying to run lichess in a docker container, but it appears that lila-ws doesn't work. In my configuration docker is installed on remote linux server. I've changed config (base.conf) and set domain and socket.domains to the name of my linux server, however web sockets seems still not working, I'm consistenly getting "Reconnecting ..." messages in the web UI. Any ideas?
I'm trying to run lichess in a docker container, but it appears that lila-ws doesn't work. In my configuration docker is installed on remote linux server. I've changed config (base.conf) and set domain and socket.domains to the name of my linux server, however web sockets seems still not working, I'm consistenly getting "Reconnecting ..." messages in the web UI. Any ideas?
You should create another issue with the outputs from your browser.
