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 new teams on the fly #16

Closed
m5rk opened this issue Jun 3, 2016 · 5 comments
Closed

Add new teams on the fly #16

m5rk opened this issue Jun 3, 2016 · 5 comments
Labels

Comments

@m5rk
Copy link

m5rk commented Jun 3, 2016

If a Team is added while the service is running, it won't be started until the next time the service is started.

@dblock
Copy link
Collaborator

dblock commented Jun 3, 2016

@dblock dblock added the bug? label Jun 3, 2016
@m5rk
Copy link
Author

m5rk commented Jun 3, 2016

@dblock That's very helpful, thank you.

I'm forced to take a piecemeal approach with slack-ruby-bot-server since I want to integrate it into an existing Rails app.

If the service is running on a multi-dyno heroku app, won't there be multiple instances of the service running, each with its own private @services hash?

@dblock
Copy link
Collaborator

dblock commented Jun 3, 2016

The multi-dyno scenario really needs a queue-based approach, see https://github.com/dblock/slack-ruby-bot-server/issues/4.

I'll close this since it's actually supported by the framework today.

@dblock dblock closed this as completed Jun 3, 2016
@BenBach
Copy link

BenBach commented Dec 12, 2017

Did someone implement a multi dyno approach already (which support dynamically creating new teams)?
Any help highly appreciated. Thank you very much :-)

@dblock
Copy link
Collaborator

dblock commented Dec 17, 2017

Not AFAIK @BenBach

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

No branches or pull requests

3 participants