You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After migration to go bridge, do we still need signaldctl?
$ sudo signaldctl account list
2024/07/09 09:44:18 dial unix /var/run/signald/signald.sock: connect: no such file or directory
:~$ sudo signaldctl version
2024/07/09 09:44:29 dial unix /var/run/signald/signald.sock: connect: no such file or directory
if not, is it safe to remove it? Shouldn't the package remove it?
How can we list SG accounts registered on the bridge now?
The text was updated successfully, but these errors were encountered:
yes, it should be safe to remove, and we can do this in the package. I would like to remove it, but I haven't really found enough time to contribute this (adding it is easy, testing is more complicated, and there are so many other things I would like to add)
signald functionality is integrated in the go rewrite, as a library. Unfortunately, I don't think there is a tool similar to signaldctl.
I think you can list registered accounts via the database: sudo -u postgres psql --dbname=mautrix_signal -c 'select * from user_login;'
MayeulC
changed the title
After migration to go bridge what is the use of signaldctl? What is replacing it?
Remove signald
Sep 30, 2024
Describe the bug
After migration to go bridge, do we still need signaldctl?
if not, is it safe to remove it? Shouldn't the package remove it?
How can we list SG accounts registered on the bridge now?
The text was updated successfully, but these errors were encountered: