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

Request: disable Nostrum startup #521

Closed
ProducerMatt opened this issue Sep 25, 2023 · 1 comment
Closed

Request: disable Nostrum startup #521

ProducerMatt opened this issue Sep 25, 2023 · 1 comment

Comments

@ProducerMatt
Copy link

I'm writing a chatbot app that supports multiple services simultaneously. So one deploy might be connected to Discord, Slack, and IRC, while another might just be IRC.

I wanted to disable Nostrum when there was no configuration for Discord. However it looks when Nostrum is in your dependencies, it is always started, unless you go jump through the hoops outlined in the multi-node setup.

I'd rather set a config flag or pass an atom to Nostrum in order to make it shut itself down.

@jchristgit
Copy link
Collaborator

You need to add nostrum to included_applications and add runtime: false to it in your mix.exs, as ni the multi-node doc. These options have no place in nostrum's configuration because they concern the way core OTP tooling deals with starting nostrum.

@ProducerMatt ProducerMatt closed this as not planned Won't fix, can't repro, duplicate, stale Sep 27, 2023
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

No branches or pull requests

2 participants