Fix #100: API endpoint enhancement

Bypassing Nginx for API call originated from Prosody (if Peertube >=5.1).
Can also fix some Docker setup, which needed to set the prosody-peertube-uri settings.

support/documentation/content/en/documentation/admin/settings.md

@@ -112,6 +112,13 @@ This settings should only be used if the plugin is broken, and waiting for a pat
 
 {{% livechat_label prosody_peertube_uri_description %}}
 
+If this settings is left empty, and you are using Peertube >= 5.1 or later, the plugin will use values from your Peertube configuration file to guess on which interface and port request have to be done.
+
+In last resort, it will use your Peertube public URI.
+So, any API Call will go throught your Nginx server.
+This could fail in some case: for example if you are in a Docker container, where the public hostname does not resolve to the correct IP.
+In such case, try changing the "{{% livechat_label prosody_peertube_uri_label %}}" settings, by setting `http://127.0.0.1:9000` (assuming 9000 is the port on which Peertube listen, ask your instance administrators if you don't know).
+
 ### {{% livechat_label prosody_muc_log_by_default_label %}}
 
 {{% livechat_label prosody_muc_log_by_default_description %}}

support/documentation/content/en/documentation/installation/troubleshooting.md

@@ -29,6 +29,8 @@ In some case (like for some Docker Peertube installation), the diagnostic tools
 
 In such case, try changing the "{{% livechat_label prosody_peertube_uri_label %}}" settings, by setting `http://127.0.0.1:9000` (assuming 9000 is the port on which Peertube listen, ask your instance administrators if you don't know).
 
+Check the help for [this settings](/peertube-plugin-livechat/documentation/admin/settings/) for more information.
+
 ### Websocket
 
 If everything is fine in the diagnostic tools, but chat windows remains empty: it can be a Websocket issue.