Replies: 1 comment
-
Oops, I didn't have this repository on my watch list and completely missed this thread. The recommended way to host the web client in production is to build it, and serve it using a web server like Nginx, however if you are trying to expose the dev port of the web client (when you are running The bot / core app itself doesn't server the web client, only the API used by the web client, so at the end you'll need to:
If you are familiar with docker, I highly recommend you to follow this guide on how to self-host your bot with web client. If you are following that tutorial, the port exposed for the web client from Nginx is 80. |
Beta Was this translation helpful? Give feedback.
-
So my internet is behind cgnat, meaning I have to do everything locally and then expose the website through a tunnel.
However, I cannot access the WebClient as I do not know the default port.
Does anyone happen to know what the default port is for the webclient?
Also does this bot support yt playlist rn or no.
Beta Was this translation helpful? Give feedback.
All reactions