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

Support multiple backends in one instance #1137

Open
jayvdb opened this Issue Nov 24, 2017 · 3 comments

Comments

Projects
None yet
3 participants
@jayvdb

jayvdb commented Nov 24, 2017

I am...

  • Reporting a bug
  • 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.

@SirEdvin

This comment has been minimized.

Show comment
Hide comment
@SirEdvin

SirEdvin Nov 28, 2017

@jayvdb Why you can't sync bot instances with help of storage? For example, with redis storage.

SirEdvin commented Nov 28, 2017

@jayvdb Why you can't sync bot instances with help of storage? For example, with redis storage.

@fernand0

This comment has been minimized.

Show comment
Hide comment
@fernand0

fernand0 Dec 2, 2017

Contributor

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.

Contributor

fernand0 commented Dec 2, 2017

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.

@jayvdb

This comment has been minimized.

Show comment
Hide comment
@jayvdb

jayvdb Dec 2, 2017

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.

jayvdb commented Dec 2, 2017

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment