mirror of
https://github.com/YunoHost-Apps/mautrix_telegram_ynh.git
synced 2024-09-03 19:45:55 +02:00
122 lines
7.2 KiB
Markdown
122 lines
7.2 KiB
Markdown
<!--
|
||
N.B.: This README was automatically generated by https://github.com/YunoHost/apps/tree/master/tools/README-generator
|
||
It shall NOT be edited by hand.
|
||
-->
|
||
|
||
# Matrix-Telegram bridge pour YunoHost
|
||
|
||
[](https://dash.yunohost.org/appci/app/mautrix_telegram)  
|
||
[](https://install-app.yunohost.org/?app=mautrix_telegram)
|
||
|
||
*[Read this readme in english.](./README.md)*
|
||
|
||
> *Ce package vous permet d'installer Matrix-Telegram bridge rapidement et simplement sur un serveur YunoHost.
|
||
Si vous n'avez pas YunoHost, regardez [ici](https://yunohost.org/#/install) pour savoir comment l'installer et en profiter.*
|
||
|
||
## Vue d'ensemble
|
||
|
||
Une passerelle entre Matrix et Telegram empaquetée comme un service YunoHost. Les messages, médias et notifications sont relayées entre un compte Telegram et un compte Matrix.
|
||
La passerelle ["Mautrix-Telegram"](https://docs.mau.fi/bridges/python/telegram/index.html) consiste en un Service d'Application Matrix-Synapse et repose sur une base-de-données postgresql. C'est pourquoi [Synapse for YunoHost](https://github.com/YunoHost-Apps/synapse_ynh) doit être préalablemnet installé.
|
||
|
||
** Attention : sauvegardez et restaurez toujours les deux applications Yunohost matrix-synapse et mautrix_telegram en même temps!**
|
||
|
||
|
||
**Version incluse :** 0.12.2~ynh3
|
||
## Avertissements / informations importantes
|
||
|
||
## Liste de passerelles publiques
|
||
|
||
* Demandez sur un des salons suivants: #mautrix_yunohost:matrix.fdn.fr ou #telegram:maunium.net
|
||
|
||
## Usages de la passerelle
|
||
** Notez que plusieurs comptes Telegram et Matrix peuvent être pontés, chaque compte Telegram connecté a son propre Salon d'Administration. Si plusieurs utilisateur.ice.s du Robot sont dans un même groupe Signal, seul un Salon Matrix sera créé par la passerelle. **
|
||
|
||
### Bridge a Telegram user and a Matrix user
|
||
* First your Matrix user or Synapse Server has to be authorized in the Configuration of the bridge (see below)
|
||
* Then, invite the bot (default @telegrambot:yoursynapse.domain) in this new Mautrix-Telegram bot administration room.
|
||
* If the Bot does bot accept, see the [troubleshooting page](https://docs.mau.fi/bridges/general/troubleshooting.html)
|
||
* Send ``!tg help`` to the bot in the created room to know how to control the bot.
|
||
See also [upstream wiki Authentication page](https://docs.mau.fi/bridges/python/telegram/authentication.html)
|
||
|
||
#### Logging into Telegram account
|
||
* Type ``login`` or ``login-qr`` (untested) in main management room (`!tg` in any bridge room)
|
||
* follow setup instructions from bot
|
||
* By defaults, only conversations with very recent messages and groups will be suggested to be bridged
|
||
* Accept invitations to the bridged chat rooms
|
||
|
||
#### Registering the Bridge as a primary device (untested)
|
||
* Type ``!tg register <phone>``, where ``<phone>`` is your phone number in the internation format with no space, e.g. ``!tg register +33612345678``
|
||
* Answer in the bot room with the verification code that you reveived in SMS.
|
||
* Set a profile name with ``!tg set-profile-name <name>``
|
||
|
||
### Double puppeting
|
||
* Log in with ``login-matrix <access token>``
|
||
* After logging in, the default Matrix puppet of your Telegram account should leave rooms and your account should join all rooms the puppet was in automatically.
|
||
|
||
|
||
### Relaybot: Bridge a group for several Matrix and several Telegram users to chat together
|
||
* see https://docs.mau.fi/bridges/python/telegram/relay-bot.html
|
||
|
||
## Documentation
|
||
|
||
* Official "Mautrix-Telegram" documentation: https://docs.mau.fi/bridges/python/telegram/index.html
|
||
* Matrix room (Matrix Bridges in Yunohost): #mautrix_yunohost:matrix.fdn.fr
|
||
* Matrix room (upstream app): #telegram:maunium.net
|
||
In case you need to upload your logs somewhere, be aware that they contain your contacts' and your phone numbers. Strip them out with
|
||
``| sed -r 's/[0-9]{10,}/??/g' ``
|
||
* "Mautrix-Telegram" bridge is based on the [telegram daemon](https://gitlab.com/telegramd/telegramd) project.
|
||
* YunoHost documentation: If more specific documentation is needed, feel free to contribute.
|
||
|
||
## Caractéristiques spécifiques YunoHost
|
||
|
||
#### Support multi-comptes
|
||
* Bot users are not related to Yunohost users. Any Matrix account or Synapse server autorized in the configuration of the bridge can invite/use the bot.
|
||
* The Telegram bot is a local Matrix-Synapse user, but accessible through federation (synapse public or private).
|
||
* Several Telegram and Matrix users can be bridged with one bridge, each user has its own bot administration room.
|
||
* If several bot users are in a same Telegram group, only one Matrix room will be created by the bridge.
|
||
* See https://github.com/YunoHost-Apps/synapse_ynh#multi-users-support
|
||
|
||
#### Support multi-instance
|
||
|
||
* Multi-instance installation should work. Several bridge instances could be installed for one Matrix-Synapse instance so that one Matrix user can bridge several Telegram accounts.
|
||
* Several bridge instances could be installed for each Matrix-Synapse instance to benefit from it. But one bridge can be used by users from several Matrix-Synapse instances.
|
||
|
||
## Troubleshooting
|
||
|
||
* Check the spelling of the bot name!
|
||
* For slow servers it might be necessary to run ``systemctl edit mautrix_telegram.service`` (also for `coturn.service` and `coturn-synapse.service`) and insert
|
||
```
|
||
[Service]
|
||
ExecStartPre=/bin/sleep 90
|
||
```
|
||
such that it is ensured that synapse is running before the bridge tries to connect.
|
||
(If it worked after installation but broke after a restart this probably is it.)
|
||
|
||
## Documentations et ressources
|
||
|
||
* Site officiel de l'app : <https://docs.mau.fi/bridges/python/telegram/index.html>
|
||
* Documentation officielle utilisateur : <https://docs.mau.fi/bridges/python/telegram/management-commands.html>
|
||
* Documentation officielle de l'admin : <https://github.com/YunoHost-Apps/mautrix_telegram_ynh>
|
||
* Dépôt de code officiel de l'app : <https://github.com/mautrix/telegram>
|
||
* Documentation YunoHost pour cette app : <https://yunohost.org/app_mautrix_telegram>
|
||
* Signaler un bug : <https://github.com/YunoHost-Apps/mautrix_telegram_ynh/issues>
|
||
|
||
## Informations pour les développeurs
|
||
|
||
Merci de faire vos pull request sur la [branche testing](https://github.com/YunoHost-Apps/mautrix_telegram_ynh/tree/testing).
|
||
|
||
Pour essayer la branche testing, procédez comme suit.
|
||
|
||
``` bash
|
||
sudo yunohost app install https://github.com/YunoHost-Apps/mautrix_telegram_ynh/tree/testing --debug
|
||
ou
|
||
sudo yunohost app upgrade mautrix_telegram -u https://github.com/YunoHost-Apps/mautrix_telegram_ynh/tree/testing --debug
|
||
```
|
||
|
||
Le script `.github/workflows/updater.sh` doit être synchronisé avec les changements dans `conf/config.yaml`,
|
||
donc pour l'instant un hook `pre-commit` est utilisé pour afficher un rappel pour mettre à jour
|
||
`.github/workflows/updater.sh` (si nécessaire) lorsque `conf/config.yaml` a été modifié.
|
||
|
||
Veuillez activer les hooks Git en utilisant la commande suivante pour assurer la qualité et la stabilité du code.
|
||
|
||
**Plus d'infos sur le packaging d'applications :** <https://yunohost.org/packaging_apps>
|