Replies: 2 comments 2 replies
-
@ashwaryy I just made you an editor, I would have done this sooner but I haven't talked to you much lately. That reminds me: What time is it for you currently its 1:03am here. I was curious about our time zone difference. |
Beta Was this translation helpful? Give feedback.
2 replies
-
@ashwaryy @ShashwatAgrawal20 @Ronnie018 https://medium.com/@ibrahimzahir7/7-websites-that-will-change-the-way-you-do-web-development-ee430c088d64 k im realy shuting this thing off Good Night Guys |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We need to explore some rules to make our Firebase backend secure. Things like only content owner should be able to write or delete data from Firestore. We have done it on frontend, but anyone can fork the repo and change the code to perform any operation on our database. This thing cannot be done on client side. We can place a few checks but there's a limit to how much validation you can do on frontend. That is why we have to make the Firestore bullet-proof by configuring security rules. Here's an article explaining how to set these up. I'll read this and run some tests.
Beta Was this translation helpful? Give feedback.
All reactions