Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove signald #114

Open
Thatoo opened this issue Jul 9, 2024 · 1 comment
Open

Remove signald #114

Thatoo opened this issue Jul 9, 2024 · 1 comment

Comments

@Thatoo
Copy link
Contributor

Thatoo commented Jul 9, 2024

Describe the bug

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?

@MayeulC
Copy link
Collaborator

MayeulC commented Sep 30, 2024

Hello,

  • 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 MayeulC changed the title After migration to go bridge what is the use of signaldctl? What is replacing it? Remove signald Sep 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants