Dockerize and fixes some bugs

[Ctrl-Mota]

No description provided.

[nizarfadlan]

Thanks for contributing. I haven't had a chance to refine this project yet.

[Ctrl-Mota]

Your unrefined work, working perfectly for my case, thanks so much Em qua., 31 de jul. de 2024 às 16:37, Nizar Izzuddin Yatim Fadlan < ***@***.***> escreveu:

…

Merged #8 <#8> into main. — Reply to this email directly, view it on GitHub <#8 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANKWY4K5I777MSFBSBI6XLLZPE4INAVCNFSM6AAAAABLZDOEHKVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJTG4YTKMJZGA2DMNI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[nizarfadlan]

Your unrefined work, working perfectly for my case, thanks so much Em qua., 31 de jul. de 2024 às 16:37, Nizar Izzuddin Yatim Fadlan < @.> escreveu:
…
Merged #8 <#8> into main. — Reply to this email directly, view it on GitHub <#8 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANKWY4K5I777MSFBSBI6XLLZPE4INAVCNFSM6AAAAABLZDOEHKVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJTG4YTKMJZGA2DMNI . You are receiving this because you authored the thread.Message ID: @.>

But why add a new reload route that contains the same logic as the add session route? And why is the function section for deleting all chats commented out, this section is made so that when the session is disconnected it means that there is no need for chat data, etc.

const destroy = async (logout = true) => {
   ...
       logout && socket.logout(),
       // prisma.chat.deleteMany({ where: { sessionId } }),
   ...
};

[Ctrl-Mota]

Sorry, I have started to develop a route for cases when contacts, messages or any data is unsynced with main whatsapp, instead of user delete session and add again. But i don't know how we receive upserts events again Em qui., 1 de ago. de 2024 às 12:27, Nizar Izzuddin Yatim Fadlan < ***@***.***> escreveu:

…

Your unrefined work, working perfectly for my case, thanks so much Em qua., 31 de jul. de 2024 às 16:37, Nizar Izzuddin Yatim Fadlan < *@*. *> escreveu: … <#m_-8569880214886137495_> Merged #8 <#8> <#8 <#8>> into main. — Reply to this email directly, view it on GitHub <#8 (comment) <#8 (comment)>>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANKWY4K5I777MSFBSBI6XLLZPE4INAVCNFSM6AAAAABLZDOEHKVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJTG4YTKMJZGA2DMNI <https://github.com/notifications/unsubscribe-auth/ANKWY4K5I777MSFBSBI6XLLZPE4INAVCNFSM6AAAAABLZDOEHKVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJTG4YTKMJZGA2DMNI> . You are receiving this because you authored the thread.Message ID: @.*> But why add a new reload route that contains the same logic as the add session route? — Reply to this email directly, view it on GitHub <#8 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANKWY4O34SYWTACV3YGUT7LZPJHVHAVCNFSM6AAAAABLZDOEHKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRTGM2TIOBXG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[nizarfadlan]

no problem okay I understand, maybe is the sync history message like a pull request in Baileys

WhiskeySockets/Baileys#919