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

Signal middleware #313

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

poplawskidaniel
Copy link

Added Signal middleware with https://github.com/bbernhard/signal-cli-rest-api usage. Approach copied from slack implementation.
Tested on my fork.
I am using that daily.

- add config example
- add logging of used middlewares (to verify if for eg. Signal config
was parsed correctly)
- fix signal config in README.md
@taraspos taraspos mentioned this pull request Feb 3, 2025
@taraspos
Copy link
Collaborator

taraspos commented Feb 3, 2025

Taking into account that bbernhard/signal-cli-rest-api is a self-hosted API wrapper around CLI, I'm not sure if it would make sense to create dedicated middleware for. Especially is API is as simple as

$ curl -X POST -H "Content-Type: application/json" 'http://localhost:8080/v2/send' \
     -d '{"message": "Test via Signal API!", "number": "+4412345", "recipients": [ "+44987654" ]}'

I don't want ofelia to end up with integration with dozens of APIs. Instead I'm wondering maybe building generic HTTP middleware with examples on how to use specific services will be better long term.

See discussion in:

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

Successfully merging this pull request may close these issues.

2 participants