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

Another dev acc or use official one #24

Open
Keyrxng opened this issue Oct 29, 2024 · 0 comments
Open

Another dev acc or use official one #24

Keyrxng opened this issue Oct 29, 2024 · 0 comments

Comments

@Keyrxng
Copy link
Collaborator

Keyrxng commented Oct 29, 2024

We only have one development bot which is the one I created through the BotFather and the MTProto account is also one that I had to register etc.

  • Anytime I need to work on things I need to take over the webhook so it's going to affect things once this starts to get used which I imagine will be as soon as the APP_PRIVATE_KEY issue is resolved because DM Notifications have been shipped and can be used now with the workaround in place
  • The workrooms feature works for us both at the same time and doesn't knock out our session which is good news. The last 24hrs have confirmed to me if we keep the connection warm we shouldn't have AUTH_KEY_DUPLICATED issues

So we should either:

A) Create another BotFather bot that can be shared and used for development.
B) Set up the official account and bot.

I'm not sure how best to handle things considering either way we're going to have to deal with sets of init values for at least two different bots so we can ensure uptime. How do we handle that elegantly, we already have a bunch of env vars, I'm a little out of my depth with the dev-ops required. @rndquu any ideas?

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

1 participant