Documentation translation (#199)
Documentation translation using weblate. * Use po4a to generate .po files from the english markdowns, then to generate translated files * Some pages can be marked as «english only» (for technical documentation for example) * New Hugo shortcode to use application strings in documentation (for example for settings names) * The code of conduct is no more translated, but there is a link to official Contributor Covenant translations * Adding all plugin's supported languages Related to https://github.com/JohnXLivingston/peertube-plugin-livechat/issues/117
This commit is contained in:
John Livingston
GitHub
8
support/documentation/content/en/documentation/_index.md
Normal file
8
support/documentation/content/en/documentation/_index.md
Normal file
@ -0,0 +1,8 @@
|
||||
---
|
||||
title: "Documentation"
|
||||
description: "Plugin documentation"
|
||||
weight: 10
|
||||
chapter: false
|
||||
---
|
||||
|
||||
{{% children depth="3" style="li" description="true" %}}
|
||||
@ -0,0 +1,8 @@
|
||||
---
|
||||
title: "Admin documentation"
|
||||
description: "Plugin Peertube Livechat administration"
|
||||
weight: 30
|
||||
chapter: false
|
||||
---
|
||||
|
||||
{{% children depth="3" style="li" description="true" %}}
|
||||
@ -0,0 +1,8 @@
|
||||
---
|
||||
title: "Advanced usage"
|
||||
description: "Some advanced features"
|
||||
weight: 20
|
||||
chapter: false
|
||||
---
|
||||
|
||||
{{% children depth="3" style="li" description="true" %}}
|
||||
@ -0,0 +1,8 @@
|
||||
---
|
||||
title: "Using Matterbridge"
|
||||
description: "Using Matterbridge to bridge with other chats"
|
||||
weight: 50
|
||||
chapter: false
|
||||
---
|
||||
|
||||
Here is a tutorial to use Matterbridge with the plugin: <https://gitlab.com/refrac/obs-matterbridge-overlay/-/blob/master/documentation/peertube.md>
|
||||
@ -0,0 +1,288 @@
|
||||
---
|
||||
title: "XMPP clients"
|
||||
description: "Allow connections using XMPP clients"
|
||||
weight: 30
|
||||
chapter: false
|
||||
---
|
||||
|
||||
This chat module is based on the XMPP protocol, also known as Jabber.
|
||||
It is therefore possible to connect to the chats using [XMPP client software](https://en.wikipedia.org/wiki/XMPP#Clients).
|
||||
This can for example be useful to facilitate moderation operations.
|
||||
|
||||
For the user documentation associated with these features, please refer to the [user documentation page](/peertube-plugin-livechat/documentation/user/xmpp_clients/).
|
||||
|
||||
{{% notice info %}}
|
||||
Enabling these features requires configuration changes on the server, and on the DNS records.
|
||||
It is not possible to configure this only from the Peertube interface, and it requires some basic system some basic system admin skills.
|
||||
{{% /notice %}}
|
||||
|
||||
## Login to your Peertube account
|
||||
|
||||
{{% notice warning %}}
|
||||
This feature is not yet available, and will come in a future version of the plugin.
|
||||
{{% /notice %}}
|
||||
|
||||
## Connection using an external XMPP account
|
||||
|
||||
To enable this feature, you will need to set up your server and DNS records, so that XMPP clients can find and access the
|
||||
[Prosody server](https://prosody.im) that this plugin uses internally.
|
||||
|
||||
### Plugin settings
|
||||
|
||||
Start by going to the livechat plugin settings of your instance, then enable the setting "Enable connection to room using external XMPP accounts".
|
||||
By checking this settings, new settings appear below.
|
||||
|
||||
First of all, the "Prosody server to server port" field.
|
||||
This one defaults to 5269, which is the standard port for this service.
|
||||
You can however change to another port, if this is already in use on your server.
|
||||
|
||||
Next, the field "Server to server network interfaces" field allows you to specify which network interfaces the server should listen on.
|
||||
The default value "*, ::" indicates to listen on all IP addresses.
|
||||
You can change these values, if you wish to listen on only certain IP addresses.
|
||||
The syntax is explained next to the setting.
|
||||
|
||||
For the "Certificate folder" setting, you can leave it empty.
|
||||
In this case, the plugin will automatically generate self-signed certificates.
|
||||
Some XMPP servers may refuse to connect, depending on their configuration.
|
||||
In this case, you can indicate here a path on the server, in which you must place certificates to be used by the module.
|
||||
It is up to you to generate and renew them.
|
||||
See bellow for more information.
|
||||
|
||||
### Firewall
|
||||
|
||||
You must open the configured port (5269 by default) on your firewall.
|
||||
|
||||
If you are using Docker for your Peertube, you need to modify the `docker-compose.yml` file to open port 5269 of the `peertube` container,
|
||||
so that the outer world can connect to it.
|
||||
|
||||
### DNS
|
||||
|
||||
You need to add a [DNS record](https://prosody.im/doc/dns) allowing remote servers to find the "room.your_instance.tld" component.
|
||||
|
||||
The easiest way to do this is to add an SRV record for the "room" [subdomain](https://prosody.im/doc/dns#subdomains):
|
||||
|
||||
* record name: _xmpp-server._tcp.room.your_instance.tld. (replace «your_instance.tld» by your instance uri)
|
||||
* TTL: 3600
|
||||
* class: IN
|
||||
* SRV: 0
|
||||
* priority: 0
|
||||
* weight: 5
|
||||
* port: 5269 (adapt if your changed the default port)
|
||||
* target: your_instance.tld. (replace by your instance uri)
|
||||
|
||||
Be careful to keep the dot after "your_instance.tld".
|
||||
|
||||
Using the `dig` command to check your record, you should get a result similar to this:
|
||||
|
||||
```bash
|
||||
$ dig +short _xmpp-server._tcp.room.videos.john-livingston.fr. SRV
|
||||
0 5 5269 videos.john-livingston.fr.
|
||||
```
|
||||
|
||||
If you are **not using the standard `5269` port**, you must also add a SRV record for `_xmpp-server._tcp.your_instance.tld.` (same as above, just without the `room.` prefix).
|
||||
Of course, you can also add this record if you use the standard port. It will also work.
|
||||
|
||||
### Using trusted certificates
|
||||
|
||||
The self-signed certificates that this plugin uses by default can be rejected by some XMPP servers, for security reasons.
|
||||
|
||||
It is possible to use certificates validated by a certification authority.
|
||||
However, this requires advanced system administration knowledge.
|
||||
Indeed, due to the multitude of possible use cases, it is impossible to document all situations here.
|
||||
This documentation will therefore only explain the goal to be reached, and give an example which will only be suitable for a "basic" situation (manual installation of Peertube, using letsencrypt).
|
||||
If you are in another situation (Docker installation, certificates signed by another authority, etc...), you will have to adapt this approach by yourself.
|
||||
|
||||
#### Basic principle
|
||||
|
||||
It is up to you to generate valid certificates for domains `your_instance.tld` and `room.your_instance.tld`.
|
||||
You can use any [method supported by Prosody](https://prosody.im/doc/certificates).
|
||||
|
||||
You must then place these certificates in a folder that will be accessible to the `peertube` user, and specify this folder in the plugin setting "Certificate folder".
|
||||
|
||||
{{% notice tip %}}
|
||||
If you want to use the ProsodyCtl utility to import certificates, this utility is available (once Peertube is started) using the following command (adapting the path to your Peertube data folder, and replacing "xxx" with the arguments you wish to pass to
|
||||
prosodyctl): `sudo -u peertube /var/www/peertube/storage/plugins/data/peertube-plugin-livechat/prosodyAppImage/squashfs-root/AppRun prosodyctl xxx`
|
||||
{{% /notice %}}
|
||||
|
||||
The plugin will check once a day to see if any files have been modified in this folder, and reload Prosody if necessary.
|
||||
|
||||
#### Method for the simple case
|
||||
|
||||
We assume here that your Peertube installation is "classic" (no use of Docker), and that the certificates are generated by letsencrypt, using the certbot tool.
|
||||
|
||||
First of all, we'll have to create a certificate for the subdomain `room.your_instance.tld` : this is the uri of the MUC (XMPP chat rooms) component.
|
||||
Even if the connections are made on `your_instance.tld`, we will need a valid certificate for this subdomain.
|
||||
|
||||
So start by setting up a DNS entry for `room.your_instance.tld`, which points to your server.
|
||||
You can use a CNAME entry (or an A entry and a AAAA entry).
|
||||
|
||||
Next, we'll use nginx (already installed for your Peertube) to generate the certbot certificate.
|
||||
We will create a new site. In the file `/etc/nginx/site-available/room.peertube`, add:
|
||||
|
||||
```nginx
|
||||
server {
|
||||
listen 80;
|
||||
listen [::]:80;
|
||||
server_name room.your_instance.tld;
|
||||
|
||||
location /.well-known/acme-challenge/ {
|
||||
default_type "text/plain";
|
||||
root /var/www/certbot;
|
||||
}
|
||||
location / { return 301 https://your_instance.tld; }
|
||||
}
|
||||
```
|
||||
|
||||
Then enable the site:
|
||||
|
||||
```bash
|
||||
ln -s /etc/nginx/sites-available/room.peertube /etc/nginx/sites-enabled/
|
||||
systemc reload nginx
|
||||
```
|
||||
|
||||
Then we prepare the folder in which we will later import the certificates.
|
||||
We assume here that you already have the plugin active. We will create the following folder (if it doesn't already exist), with the user `peertube` to make sure there are no permissions issues:
|
||||
|
||||
```bash
|
||||
sudo -u peertube mkdir /var/www/peertube/storage/plugins/data/peertube-plugin-livechat/prosody/certs
|
||||
```
|
||||
|
||||
Now you have to configure this folder in the plugin settings, for the parameter "Certificate folders".
|
||||
It's important to do this now, otherwise the certificate import script will put the certificates in the wrong folder.
|
||||
|
||||
We will configure certbot to import the generated certificates into the Prosody folder.
|
||||
We can use the ProsodyCtl utility packaged in the plugin.
|
||||
|
||||
Note: for it to be available, the plugin must have been started at least once.
|
||||
|
||||
We will create a file `/etc/letsencrypt/renewal-hooks/deploy/prosody.sh` containing:
|
||||
|
||||
```bash
|
||||
#!/bin/sh
|
||||
/var/www/peertube/storage/plugins/data/peertube-plugin-livechat/prosodyAppImage/squashfs-root/AppRun prosodyctl \
|
||||
--root \
|
||||
--config /var/www/peertube/storage/plugins/data/peertube-plugin-livechat/prosody/prosody.cfg.lua \
|
||||
cert import \
|
||||
room.your_instance.tld your_instance.tld /etc/letsencrypt/live
|
||||
```
|
||||
|
||||
Then we ask to generate the certificate:
|
||||
|
||||
```bash
|
||||
certbot -d room.videos.john-livingston.fr
|
||||
```
|
||||
|
||||
If certbot offers you several methods to generate the certificate, choose "nginx".
|
||||
|
||||
Normally you should now find the certificates in the configured folder.
|
||||
|
||||
Note: the first time you do this, you will have to reload Prosody. The easiest way to do this is to restart Peertube.
|
||||
|
||||
#### Method for the Docker case
|
||||
|
||||
This method works with the officially supported [Docker guide](https://docs.joinpeertube.org/install/docker) from PeerTube.
|
||||
|
||||
First, ensure you create a DNS entry for `room.your_instance.tld`, which points to your server.
|
||||
You can use a CNAME entry (or an A entry and a AAAA entry).
|
||||
This is necessary for Let's Encrypt to validate the domain for certificate generation.
|
||||
|
||||
Enter the directory where your `docker-compose.yml` file exists.
|
||||
|
||||
Open a shell in the certbot container:
|
||||
|
||||
```bash
|
||||
docker exec -it certbot /bin/sh
|
||||
```
|
||||
|
||||
Run certbot:
|
||||
|
||||
```bash
|
||||
certbot
|
||||
```
|
||||
|
||||
You will be presented with a series of prompts. Enter `2` for the authentication type:
|
||||
|
||||
```text
|
||||
How would you like to authenticate with the ACME CA?
|
||||
Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 2
|
||||
```
|
||||
|
||||
Enter the domain name `room.your_instance.tld`:
|
||||
|
||||
```text
|
||||
Please enter the domain name(s) you would like on your certificate (comma and/or space separated) (Enter 'c' to cancel): room.your_instance.tld
|
||||
```
|
||||
|
||||
Enter the directory where the PeerTube webserver serves requests for Let's Encrypt, `/var/www/certbot`:
|
||||
|
||||
```text
|
||||
Input the webroot for <room.your_instance.tld>: (Enter 'c' to cancel): /var/www/certbot
|
||||
```
|
||||
|
||||
You should see output like the following:
|
||||
|
||||
```text
|
||||
Successfully received certificate.
|
||||
Certificate is saved at: /etc/letsencrypt/live/room.your_instance.tld/fullchain.pem
|
||||
Key is saved at: /etc/letsencrypt/live/room.your_instance.tld/privkey.pem
|
||||
```
|
||||
|
||||
Run the below command inside the certbot container to give read access to the new certs and private keys to the peertube group.
|
||||
*Note*: This will also make the files readable to the group with id 999 on the host system.
|
||||
Check the groups on your system to assess this as a risk before running this command.
|
||||
|
||||
```bash
|
||||
chown -R root:999 /etc/letsencrypt/live; \
|
||||
chmod 750 /etc/letsencrypt/live; \
|
||||
chown -R root:999 /etc/letsencrypt/archive; \
|
||||
chmod 750 /etc/letsencrypt/archive; \
|
||||
find /etc/letsencrypt/ -name 'privkey*' -exec chmod 0640 {} \;
|
||||
```
|
||||
|
||||
Exit the certbot container:
|
||||
|
||||
```bash
|
||||
exit
|
||||
```
|
||||
|
||||
Modify your `docker-compose.yml` file, changing the `entrypoint` line under the `certbot` service to the following.
|
||||
This is the same as the above, but to be automatically executed after every certificate renewal.
|
||||
|
||||
```text
|
||||
entrypoint: /bin/sh -c "trap exit TERM; while :; do certbot renew --webroot -w /var/www/certbot; chown -R root:999 /etc/letsencrypt/live; chmod 750 /etc/letsencrypt/live; chown -R root:999 /etc/letsencrypt/archive; chmod 750 /etc/letsencrypt/archive; find /etc/letsencrypt/ -name 'privkey*' -exec chmod 0640 {} +; sleep 12h & wait $${!}; done;"
|
||||
```
|
||||
|
||||
Continuing to modify `docker-compose.yml`, add the certbot certificate volume into the peertube container.
|
||||
It should look something like this:
|
||||
|
||||
```text
|
||||
volumes:
|
||||
- ./docker-volume/certbot/conf:/etc/letsencrypt
|
||||
```
|
||||
|
||||
Restart your services:
|
||||
|
||||
```bash
|
||||
docker-compose down; docker-comopse up -d
|
||||
```
|
||||
|
||||
In the livechat plugin settings from your PeerTube administration settings, set the certificate directory to the following:
|
||||
|
||||
```text
|
||||
/etc/letsencrypt/live
|
||||
```
|
||||
|
||||
Save the plugin settings and verify Prosody can see the certificates:
|
||||
|
||||
```bash
|
||||
docker-compose exec -u peertube \
|
||||
peertube \
|
||||
/data/plugins/data/peertube-plugin-livechat/prosodyAppImage/squashfs-root/AppRun \
|
||||
prosodyctl \
|
||||
--config /data/plugins/data/peertube-plugin-livechat/prosody/prosody.cfg.lua \
|
||||
check certs
|
||||
```
|
||||
|
||||
### Troubleshooting
|
||||
|
||||
If you can't make it work, you can use the diagnostic tool (there is a button on top of the plugin settings page), and take a close look on the «Prosody check» section.
|
||||
159
support/documentation/content/en/documentation/admin/settings.md
Normal file
159
support/documentation/content/en/documentation/admin/settings.md
Normal file
@ -0,0 +1,159 @@
|
||||
---
|
||||
title: "Settings"
|
||||
description: "Plugin Peertube Livechat settings"
|
||||
weight: 10
|
||||
chapter: false
|
||||
---
|
||||
|
||||
This section describes the plugin settings page.
|
||||
|
||||
## {{% livechat_label "list_rooms_label" %}}
|
||||
|
||||
When pressing the «List rooms» button, all existing chatrooms will be listed.
|
||||
You can then find them and moderated them.
|
||||
|
||||
## Federation
|
||||
|
||||
Following settings concern the federation with other Peertube instances, and other fediverse softwares.
|
||||
|
||||
### {{% livechat_label federation_no_remote_chat_label %}}
|
||||
|
||||
{{% livechat_label federation_no_remote_chat_description %}}
|
||||
|
||||
### {{% livechat_label federation_dont_publish_remotely_label %}}
|
||||
|
||||
{{% livechat_label federation_dont_publish_remotely_description %}}
|
||||
|
||||
## Chat behaviour
|
||||
|
||||
### {{% livechat_label room_type_label %}}
|
||||
|
||||
{{% livechat_label room_type_description %}}
|
||||
|
||||
### {{% livechat_label auto_display_label %}}
|
||||
|
||||
{{% livechat_label auto_display_description %}}
|
||||
|
||||
### {{% livechat_label open_blank_label %}}
|
||||
|
||||
{{% livechat_label open_blank_description %}}
|
||||
|
||||
### {{% livechat_label share_url_label %}}
|
||||
|
||||
This feature enables a «share chat link» modal. With this modal, you can generate URLs to join the chat.
|
||||
The chat can be customized (readonly mode, use the current theme, ...).
|
||||
|
||||
You can for example generate a readonly URL and use it in OBS to integrate the chat in your live stream!
|
||||
|
||||
This settings allows you to choose who can access this modal.
|
||||
|
||||
### {{% livechat_label per_live_video_label %}}
|
||||
|
||||
{{% livechat_label per_live_video_description %}}
|
||||
|
||||
The video owner will be able to activate web chats.
|
||||
|
||||
### {{% livechat_label all_lives_label %}}
|
||||
|
||||
{{% livechat_label all_lives_description %}}
|
||||
|
||||
### {{% livechat_label all_non_lives_label %}}
|
||||
|
||||
{{% livechat_label all_non_lives_label %}}
|
||||
|
||||
### {{% livechat_label videos_list_label %}}
|
||||
|
||||
{{% livechat_label videos_list_label %}}
|
||||
|
||||
### {{% livechat_label no_anonymous_label %}}
|
||||
|
||||
{{% livechat_label no_anonymous_description %}}
|
||||
|
||||
Note: for now this feature simply hide the chat.
|
||||
In a future release, the chat will be replaced by a message saying «please log in to [...]».
|
||||
See [v5.7.0 Release Notes](https://github.com/JohnXLivingston/peertube-plugin-livechat/blob/main/CHANGELOG.md#570) for more information.
|
||||
|
||||
## Theming
|
||||
|
||||
### {{% livechat_label converse_theme_label %}}
|
||||
|
||||
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 concord theme: this is a theme provided by ConverseJS.
|
||||
|
||||
### {{% livechat_label autocolors_label %}}
|
||||
|
||||
{{% livechat_label autocolors_description %}}
|
||||
|
||||
### {{% livechat_label chat_style_label %}}
|
||||
|
||||
{{% livechat_label chat_style_description %}}
|
||||
|
||||
## Chat server advanced settings
|
||||
|
||||
### {{% livechat_label system_prosody_label %}}
|
||||
|
||||
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 settings should only be used if the plugin is broken, and waiting for a patch.
|
||||
|
||||
### {{% livechat_label disable_websocket_label %}}
|
||||
|
||||
{{% livechat_label disable_websocket_description %}}
|
||||
|
||||
### {{% livechat_label prosody_port_label %}}
|
||||
|
||||
{{% livechat_label prosody_port_description %}}
|
||||
|
||||
### {{% livechat_label prosody_peertube_uri_label %}}
|
||||
|
||||
{{% livechat_label prosody_peertube_uri_description %}}
|
||||
|
||||
### {{% livechat_label prosody_muc_log_by_default_label %}}
|
||||
|
||||
{{% livechat_label prosody_muc_log_by_default_description %}}
|
||||
|
||||
### {{% livechat_label prosody_muc_expiration_label %}}
|
||||
|
||||
{{% livechat_label prosody_muc_expiration_description %}}
|
||||
|
||||
### {{% livechat_label prosody_room_allow_s2s_label %}}
|
||||
|
||||
{{% livechat_label prosody_room_allow_s2s_description %}}
|
||||
|
||||
### {{% livechat_label prosody_s2s_port_label %}}
|
||||
|
||||
{{% livechat_label prosody_s2s_port_description %}}
|
||||
|
||||
### {{% livechat_label prosody_s2s_interfaces_label %}}
|
||||
|
||||
{{% livechat_label prosody_s2s_interfaces_description %}}
|
||||
|
||||
### {{% livechat_label prosody_certificates_dir_label %}}
|
||||
|
||||
{{% livechat_label prosody_certificates_dir_description %}}
|
||||
|
||||
### {{% livechat_label prosody_c2s_label %}}
|
||||
|
||||
{{% livechat_label prosody_c2s_description %}}
|
||||
|
||||
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.
|
||||
|
||||
#### {{% livechat_label prosody_c2s_port_label %}}
|
||||
|
||||
{{% livechat_label prosody_c2s_port_description %}}
|
||||
|
||||
### {{% livechat_label prosody_components_label %}}
|
||||
|
||||
This settings enable XMPP external components to connect to the server.
|
||||
For now, this option **only allows connections from localhost components**.
|
||||
|
||||
This feature could be used to connect bridges or bots.
|
||||
|
||||
More informations on Prosody external components [here](https://prosody.im/doc/components).
|
||||
@ -0,0 +1,18 @@
|
||||
---
|
||||
title: "Installation guide"
|
||||
description: "Plugin peertube-plugin-livechat installation guide"
|
||||
weight: 10
|
||||
chapter: false
|
||||
---
|
||||
|
||||
{{% notice info %}}
|
||||
Before updating to a major release, please read the release notes and breaking changes list : [CHANGELOG](https://github.com/JohnXLivingston/peertube-plugin-livechat/blob/main/CHANGELOG.md).
|
||||
{{% /notice %}}
|
||||
|
||||
{{% notice tip %}}
|
||||
To install or update the plugin, **just use the Peertube web admin interface**.
|
||||
{{% /notice %}}
|
||||
|
||||
Here are some other more specific instructions:
|
||||
|
||||
{{% children style="li" depth="3" description="true" %}}
|
||||
@ -0,0 +1,59 @@
|
||||
---
|
||||
title: "Known issues: CPU Compatibility"
|
||||
description: "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."
|
||||
weight: 10
|
||||
chapter: false
|
||||
---
|
||||
|
||||
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.
|
||||
|
||||
For example, on Debian/Ubuntu:
|
||||
|
||||
```bash
|
||||
sudo apt install prosody
|
||||
```
|
||||
|
||||
You can then disable the service that starts automatically when you install Prosody (the plugin will launch a Prosody process, there is no need for the service to run).
|
||||
For example, on Debian/Ubuntu (and other Systemd based linux distributions):
|
||||
|
||||
```bash
|
||||
sudo systemctl disable prosody && sudo systemctl stop prosody
|
||||
```
|
||||
|
||||
Warning: do not disable Prosody if it is used for another service on your server, like for example Jitsi.
|
||||
|
||||
## Docker
|
||||
|
||||
You will have to generate a Peertube image that includes Prosody in the same container that Peertube.
|
||||
I know this is not the standard way to do this with Docker, but keep in mind it is a temporary workaround.
|
||||
|
||||
To generate and use such an image, please refer to the Docker documentation.
|
||||
The Docker file to generate the image should be:
|
||||
|
||||
```Docker
|
||||
FROM chocobozzz/peertube:production-bullseye
|
||||
|
||||
RUN apt -y update && apt install -y prosody && apt -y clean
|
||||
```
|
||||
|
||||
## Yunohost
|
||||
|
||||
You have to disable `metronome` (the XMPP server provided by Yunohost), and install `prosody`.
|
||||
|
||||
This is already done by the Yunohost Peertube application, as it was required for the plugin before the v6.0.0.
|
||||
|
||||
But it may be removed in a near feature (to avoid drawbacks of this method).
|
||||
I have to discuss with Yunohost team, to decide how we can do to minimize drawbacks, and maximize compatibility.
|
||||
@ -0,0 +1,14 @@
|
||||
---
|
||||
title: "Upgrade from version older than 6.0.0"
|
||||
description: "Important notes when upgrading for an older version."
|
||||
weight: 50
|
||||
chapter: false
|
||||
---
|
||||
|
||||
## IMPORTANT NOTE
|
||||
|
||||
Since version v6.0.0, this plugin does not need any Prosody installation.
|
||||
|
||||
If you were using this plugin before this version, and if you had installed Prosody manually, you can safely uninstall Prosody.
|
||||
|
||||
If you were using the custom Peertube docker image that is embedding Prosody, you can switch back to the official Peertube image.
|
||||
@ -0,0 +1,8 @@
|
||||
---
|
||||
title: "User documentation"
|
||||
description: "Plugin peertube-plugin-livechat user documentation"
|
||||
weight: 40
|
||||
chapter: false
|
||||
---
|
||||
|
||||
{{% children depth="3" style="li" description="true" %}}
|
||||
@ -0,0 +1,21 @@
|
||||
---
|
||||
title: "Moderation"
|
||||
description: "Plugin peertube-plugin-livechat moderation"
|
||||
weight: 10
|
||||
chapter: false
|
||||
---
|
||||
|
||||
You can access room settings and moderation tools by opening the chat in a new window,
|
||||
and using the dropdown menu at the top right.
|
||||
|
||||
You can list all existing chatrooms: in the plugin settings screen, there is a button «List rooms».
|
||||
|
||||
You can delete old rooms: join the room, and use the menu on the top to destroy the room.
|
||||
|
||||
## Notes
|
||||
|
||||
All instance moderators and admins will be owner of created chat rooms.
|
||||
If the video is local (not from a remote Peertube), the video owner will be admin in the chat room.
|
||||
|
||||
You can use [ConverseJS moderation commands](https://conversejs.org/docs/html/features.html#moderating-chatrooms) to moderate the room.
|
||||
When you open the chat room in full screen, there will also be a menu with dedicated commands on the top right.
|
||||
34
support/documentation/content/en/documentation/user/obs.md
Normal file
34
support/documentation/content/en/documentation/user/obs.md
Normal file
@ -0,0 +1,34 @@
|
||||
---
|
||||
title: "OBS"
|
||||
description: "Documentation to stream the chat content using OBS."
|
||||
weight: 10
|
||||
chapter: false
|
||||
---
|
||||
|
||||
## OBS Overlay
|
||||
|
||||
If you are using OBS for streaming, you can easily include the chat in your stream.
|
||||
|
||||
You can use the «share chat link» feature to generate an URL to your chat.
|
||||
The button should be near the chat if you are the video owner (unless it was desactivated by your server admins).
|
||||
|
||||
Check the «readonly» checkbox in the modal.
|
||||
Then use this link as a «web browser source» in OBS.
|
||||
|
||||
You can use the «Transparent background» to have a transparent background in OBS.
|
||||
If you want to customize the background transparency, you can add this CSS in your OBS browser source's settings:
|
||||
|
||||
```css
|
||||
:root {
|
||||
--livechat-transparent: rgba(255 255 255 / 90%) !important;
|
||||
}
|
||||
```
|
||||
|
||||
Note: you can customize colors. This is undocumented yet, but you can try this:
|
||||
in the modal, check «use curent theme colors», then you can try to manually change color values in the URL.
|
||||
You must use valid CSS color values, and they must be properly URL encoded.
|
||||
|
||||
## Mixing multiple chats in your live stream
|
||||
|
||||
You can use the [social_stream browser extension](https://github.com/steveseguin/social_stream#readme) to mix multiple chat source (from Peertube, Twitch, Youtube, Facebook, ...) and include their contents in your live stream.
|
||||
The compatibility with this plugin was added in recent versions.
|
||||
@ -0,0 +1,45 @@
|
||||
---
|
||||
title: "XMPP Clients"
|
||||
description: "Connect to chat using a XMPP client"
|
||||
weight: 40
|
||||
chapter: false
|
||||
---
|
||||
|
||||
This chat plugin relies on the XMPP protocol (also known as Jabber).
|
||||
It is therefore possible to connect to the chats using
|
||||
[XMPP client software](https://en.wikipedia.org/wiki/XMPP#Clients).
|
||||
This can be useful for example to facilitate moderation operations.
|
||||
|
||||
{{% notice info %}}
|
||||
The features described on this page must be enabled and configured by
|
||||
your Peertube instance's administrators. You may therefore not have access to them.
|
||||
{{% /notice %}}
|
||||
|
||||
## Login to your Peertube account
|
||||
|
||||
{{% notice warning %}}
|
||||
This feature is not yet available, and will come in a future version of the plugin.
|
||||
{{% /notice %}}
|
||||
|
||||
## Connection using an external XMPP account
|
||||
|
||||
If this feature is enabled on your instance, you can connect to Peertube
|
||||
chats using any XMPP account.
|
||||
|
||||
To get the address of the room you want to join, you can use the "share chat"
|
||||
button that is located above the chat:
|
||||
|
||||
|
||||
|
||||
{{% notice info %}}
|
||||
By default, the share button is only visible to the owner of the video,
|
||||
and the admins/moderators of the instance.
|
||||
However, admins can decide to display this button for everyone.
|
||||
{{% /notice %}}
|
||||
|
||||
Then, choose "Connect using XMPP":
|
||||
|
||||
|
||||
|
||||
Then you just have to click on "open" or copy/paste the address of the chat room into your XMPP client
|
||||
(using the "join a room" feature).
|
||||
Reference in New Issue
Block a user