Redis db connected through API endpoint updates when I'm running on localhost but not on deployments
Answered
English Angora posted this in #help-forum
English AngoraOP
See the original link for code and context:
https://nextjs-forum.com/post/1183108969212940418
I updated the message regex to accept newline characters btw.
https://nextjs-forum.com/post/1183108969212940418
I updated the message regex to accept newline characters btw.
Answered by English Angora
Well this database was actually updating but I think the reason why I wasn't seeing it in the CLI immediately was that over 500 DUPLICATE MESSAGES WERE BEING SENT
7 Replies
can you provide more information, to make the problem solvable? 🙂
English AngoraOP
I'm not sure what else to say🤔. I've had an issue before where my global styles work on localhost for MUI components, but didnt work when deployed. Supposedly it might have had to do with race conditions with another library where some other library controlled the styles first on the deployment and not on localhost. Maybe something like that is happening with redis or my API route.
I am using base64 encoding and decoding in the query parameters in the API route. Maybe there is some incompatibility with that?
thanks for the clarify. I can't help you with that. Good luck! 🙂
English AngoraOP
https://stackoverflow.com/questions/76356803/data-not-updating-when-deployed-nextjs13-app-on-vercel-despite-using-cache-no maybe force-dynamic might work. I'm going to try it.
English AngoraOP
Well this database was actually updating but I think the reason why I wasn't seeing it in the CLI immediately was that over 500 DUPLICATE MESSAGES WERE BEING SENT
Answer
English AngoraOP
🖕to whoever did that (if it was intentional). I just had to disconnect my database