Open shauns opened 6 years ago
Currently everything is local and in memory. You would have to find another way to hold conversational state, for example state machines, and save them in a shared database.
Sorry, but there is nothing on the roadmap pushing for this sort of thing. Let me know if you have any more questions. I'll leave this open for a bit in case someone has any good suggestions.
Any examples as to the best practices for saving responses in a database?
Is anybody using this library in production with multiple worker processes?
I wondered how people are handling conversation state when the bot is behind a load balancer. At the moment, it seems that
Bootbot._conversations
relies on local state.