-
-
Notifications
You must be signed in to change notification settings - Fork 241
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
[feature] Remote auth storage (mongo) #41
Comments
Hi, thank you for letting us know! We'll look at this! For other who are interested in the feature - please hit thumbs up emoji in the above comment👍 |
Thanks @allburov ! Any news on this front? This would be a huge reason for us to get a plus subscription. :) |
Hi! If you subscribe now - it'll help the project anyway and give us more time for the project and the feature!😉 |
Subscribed on patreon already :) |
Hey, any update on this issue? Abt to develop it on my own |
Hi! We're planning to implement it in September\October, hopefully! |
Any updates for chats on NOWEB engine? |
Hi! It's the most important task for 2024, hopefully we'll add it soon! |
Hi! This feature is now available as part of the WAHA Plus offering. We have documented the feature and its usage in our documentation, available at Session Storage. To get started with the MongoDB storage, you can follow these simple steps: First, start the MongoDB server by running the following command: docker run -d -p 27017:27017 --name mongodb mongo Next, initiate the WAHA with the docker run -e WHATSAPP_SESSIONS_MONGO_URL=mongodb://localhost:27017/ --network host devlikeapro/whatsapp-http-api-plus Following these steps, you will have successfully configured the MongoDB storage for WAHA. All session authentication data will now be stored in the MongoDB database. For those of you eager to test this new feature, we would like to stress the importance of thoroughly testing MongoDB storage before deploying it in any production-related infrastructure. |
No description provided.
The text was updated successfully, but these errors were encountered: