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

Add proper multi-server support #45

Open
joaodforce opened this issue Feb 4, 2020 · 3 comments
Open

Add proper multi-server support #45

joaodforce opened this issue Feb 4, 2020 · 3 comments
Labels
Epic This issue is an Epic.
Milestone

Comments

@joaodforce
Copy link
Contributor

The current implementation of the BOT is not suitable to be used across multiple servers. The following topics should be addressed before it can do such thing:

  • Implement server aware bill monitoring.
  • Implement server aware configurations.
  • Implement server aware LegiScan API Access.
  • Implement a way to each server provide their own LegiScan API securely.
@finnbear
Copy link
Member

finnbear commented Feb 5, 2020

storing a separate database.json for each server would solve most of the issues. the file name could even be the server id.

@finnbear finnbear added this to the V2 milestone Feb 5, 2020
@x47188 x47188 added the Epic This issue is an Epic. label Feb 5, 2020
@j1mbl3s
Copy link
Contributor

j1mbl3s commented Feb 5, 2020

storing a separate database.json for each server would solve most of the issues. the file name could even be the server id.

Could get even more granular and have a database.json per channel. Including DMs.

@finnbear
Copy link
Member

finnbear commented Feb 6, 2020

storing a separate database.json for each server would solve most of the issues. the file name could even be the server id.

Could get even more granular and have a database.json per channel. Including DMs.

That would be good for DMs, but not for servers. Servers might like a legiscan output channel and a legiscan config channel.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Epic This issue is an Epic.
Projects
None yet
Development

No branches or pull requests

4 participants