errbot
errbot copied to clipboard
Support multiple backends in one instance
I am...
- [ ] Reporting a bug
- [x] Suggesting a new feature
- [ ] Requesting help with running my bot
- [ ] Requesting help writing plugins
- [ ] Here about something else
Issue description
It should be possible to have one bot working on multiple backends concurrently. Obviously not an easy task, but increasingly important that teams operate in multiple chat systems, bridges often confuse bots, and running multiple instances for each backend is problematic if there is any state in the bot.
@jayvdb Why you can't sync bot instances with help of storage? For example, with redis storage.
It would be a nice option. Nevertheless there was a poll https://plus.google.com/+ErrbotNet/posts/3oDqwKXzdCa and it was not very popular. As I'm a believer of this multchannel question I'm thinking about the possibility of having several bots in different backends and having some communication among them in some common channel.
Hi @SirEdvin , for smallish communities, having one bot per chat system , and then adding redis , is extra stuff to manage and/or pay for. errbot already has basic bridging capabilities from what I've read (never tried it), so it seems like a natural application of the "0, 1, many rule" that errbot's internal system should be able to handle this.
Is there any progress on it? I'm interested in this issue's proposal.
If possible, I hope errbot would support multiple backends in one instance.
There has been no development effort towards this.
We will gladly accept PRs toward this.
@jayvdb Why you can't sync bot instances with help of storage? For example, with redis storage.
Is there a guide somewhere for this? What would be the limitations of such an approach?