Zen

Traduction

Anglais type: Plain text
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).
0/4810 · 481

Connectez-vous pour enregistrer vos traductions.

Anglais Occitan Actions
{{% livechat_label avatar_set_option_fenec %}}: [David Revoy's fenec/mobilizon avatar generator](https://www.peppercarrot.com/extras/html/2020_mobilizon-generator/), [CC-By](https://creativecommons.org/licenses/by/4.0/) license
 
![Fenecs avatar example](/peertube-plugin-livechat/images/avatar_fenec.png?classes=shadow,border&height=40px "Fenecs")
 
{{% livechat_label avatar_set_option_abstract %}}: [David Revoy's Abstract avatar generator](https://www.peppercarrot.com/extras/html/2017_abstract-generator/index.php), [CC-By](https://creativecommons.org/licenses/by/4.0/) license
 
![Abstracts avatar example](/peertube-plugin-livechat/images/avatar_abstract.png?classes=shadow,border&height=40px "Abtracts")
 
{{% livechat_label avatar_set_option_legacy %}}: Based on [David Revoy' work](https://www.davidrevoy.com), [AGPL-v3](https://www.gnu.org/licenses/agpl-3.0.en.html) license
 
![Legacy avatar example](/peertube-plugin-livechat/images/avatar_legacy.jpg?classes=shadow,border&height=40px "Legacy")
 
If you can't see the change immediatly, it could be because of your browser cache. Just clear your browser session storage, or restart it.
 
You can choose which theme to use for ConverseJS:
 
Peertube theme: this is a special theme, made especially for peertube's integration.
 
Default ConverseJS theme: this is the default ConverseJS theme.
 
ConverseJS cyberpunk theme: this is a theme provided by ConverseJS.
 
Chat server advanced settings
 
The plugin comes with an AppImage that is used to run the [Prosody XMPP server](https://prosody.im). If this AppImage is not working, you can fallback to the Prosody that is packaged for your server. Just install the `prosody` package.
 
This setting should only be used if the plugin is broken, and waiting for a patch.
 
If this setting 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).
 
This setting enable XMPP clients to connect to the built-in Prosody server. For now, this option **only allows connections from localhost clients**.
 
As example, this option can allow an instance of Matterbridge (once it could use anonymous login) *on the same machine* to bridge your chat with another services like a Matrix room.
 
This setting enable XMPP external components to connect to the server. By default, this option **only allows connections from localhost components**. You have to change the "{{% livechat_label prosody_components_interfaces_label %}}" value to listen on other network interfaces.
 
This feature could be used to connect bridges or bots.
 
More informations on Prosody external components [here](https://prosody.im/doc/components).
 
For more information, please check [the documentation](/peertube-plugin-livechat/documentation/admin/mod_firewall/).
 
Plugin documentation
 
For now, the plugin only works out of the box for x86_64 and arm64 CPU architecture. Here are some instructions for other CPU architectures.
 
Known issues: CPU Compatibility
 
The Prosody AppImage included in the plugin will only work on x86_64 and arm64 CPU. It is not compatible with other CPU architectures.
 
To use the plugin, you will have to manually install Prosody on your server (see below).
 
Note: the plugin requires Prosody >= 0.12.0.
If you are using an older version, Chat Federation could be broken, and it could have some unexpected behaviour.
 
Once it is done, you have to check `Use system Prosody` in the plugin settings.
 
On non-docker Peertube installation
 
For standard installation, you just have to install the official `prosody` package for your linux distribution.
 

Chargement…

Avatar de l’utilisateur Aucun

Chaîne mise à jour dans le dépôt
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).
 
Il y a un an
Parcourir toutes les modifications de chaînes

Glossaire

Anglais Occitan
instance instància PeerTube
is es PeerTube
last darrèr-a / darrièr-a PeerTube
not pas PeerTube
on en PeerTube
the lo-a-s PeerTube
this aquest-a PeerTube
you tu / vos PeerTube
your vòstre-a PeerTube

Informations sur la chaîne

Description de la chaîne source
type: Plain text
Emplacement de la chaîne source
build/documentation/pot_in/documentation/admin/settings.md
Âge de la chaîne
Il y a un an
Date de dernière mise à jour
Il y a un mois
Âge de la chaîne source
Il y a un an
Fichier de traduction
support/documentation/po/livechat.oc.po, chaîne 394