Search Criteria
Package Details: mautrix-whatsapp 0.11.2-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/mautrix-whatsapp.git (read-only, click to copy) |
|---|---|
| Package Base: | mautrix-whatsapp |
| Description: | A Matrix-WhatsApp puppeting bridge |
| Upstream URL: | https://github.com/tulir/mautrix-whatsapp |
| Licenses: | AGPL-3.0-or-later |
| Submitter: | L0ric0 |
| Maintainer: | sukanka |
| Last Packager: | sukanka |
| Votes: | 10 |
| Popularity: | 0.038798 |
| First Submitted: | 2020-12-31 15:10 (UTC) |
| Last Updated: | 2024-12-19 14:45 (UTC) |
Dependencies (4)
- libolm (libolm-gitAUR)
- git (git-gitAUR, git-glAUR) (make)
- go (go-gitAUR, gcc-go-gitAUR, gcc-go-snapshotAUR, gcc-go) (make)
- ffmpeg (ffmpeg-nvcodec-11-1-gitAUR, ffmpeg-cudaAUR, ffmpeg-fullAUR, ffmpeg-decklinkAUR, ffmpeg-amd-fullAUR, ffmpeg-ffplayoutAUR, ffmpeg-full-gitAUR, ffmpeg-gitAUR, ffmpeg-headlessAUR, ffmpeg-amd-full-gitAUR, ffmpeg-obsAUR, ffmpeg-libfdk_aacAUR) (optional) – If you want to send gifs from Matrix
Latest Comments
« First ‹ Previous 1 2 3
logolive commented on 2021-05-22 07:05 (UTC)
I have had the service crash due to a bug I am still trying to hunt down. The problem is that in Matrix there is no indication that this happened, at least no automatic one, so the user will never know that he is missing messages and not communicating with anyone on WhatsApp.
As a temporary fix and a general idea going forward, what is your opinion to making the service file restart the service upon crash (Restart=on-failure)?
podiki commented on 2021-03-05 19:41 (UTC)
For the database, could have the
mautrix-whatsappuser have a home directory (e.g./var/lib/mautrix-whatsapp) which I've seen for some other bridges. That would then be the working directory for the service.As for permissions, you are right, that is a better idea and also seems to be common among other bridges now that I've got them set up. That works for me, and unless bridges decide to formalize a shared registration directory, is probably the cleanest.
L0ric0 commented on 2021-03-04 19:12 (UTC)
i will lock into moving the database to the directory when i have time.
regarding the registration file. I have normaly handled it by adding the
synapseuser to themautrix-whatsappgroup. which is in my opinion the safest option as everyone that has access to the registration file has (as far as i know) a lot of unresticted access to the homeserver. Also it is not realy possible to put theregistration.yamlfile into asynapseowned directory as other homeservers are starting to add appservice support and so the package can't asume that you have synapse installed. Another option would be to reach a consensus with all the other packages that add appservices for a matrix homeserver for a single canonical directory for registration files.podiki commented on 2021-02-28 17:18 (UTC)
I think it would be handy to have a directory for the database (and any other files needing to be written by the bridge). So I created one in
/var/lib/owned bymautrix-whatsappand set that as the working director and readwrite permissions in the service. Maybe also include some of the service settings from the docs? https://docs.mau.fi/bridges/go/whatsapp/setup/systemd.htmlAlso (true with I think all the bridges I've tried) there are permissions needed for synapse to read the created
registration.yamlfile (if made in the/etc/mautrix-whatsappdirector). Not sure if normally this is put in a synapse directory or just owned by synapse or made world readable?« First ‹ Previous 1 2 3