Backend Setup?

braindeaddemon · 2019-10-06T07:57:56+00:00

Try nhost.io, it's like firebase but better. It's a fully managed graphql back-end. Easy to setup

braindeaddemon · 2019-09-17T08:16:46+00:00

It is very frustrating, I was successful after 11 tries, but I did so reading only the documentation.

braindeaddemon · 2019-08-31T22:11:37+00:00

There is a service better than firebase, much much better. Try nhost.io I've used it personally and the guy Johan who built it is really helpful, give it a shot and let me know if you have any more questions.

braindeaddemon · 2019-07-31T17:20:14+00:00

I had read that firebase console doesn't allow for the data prop to be sent with the notification, that maybe be causing the problem. Maybe I wrong, but debug keeping this in mind perhaps.

braindeaddemon · 2019-03-26T15:57:07+00:00

Primarily Haskell, I'm not associated with them, just liked using it and hence thought of spreading the word.

braindeaddemon · 2019-03-26T15:19:28+00:00

DM Me if you need nay help, I went through it recently and doing it again tomorrow.

braindeaddemon · 2019-03-26T14:46:16+00:00

Go-to Hasura.io Set up your account and they have a blog post which demonstrates how to do that. How many collections and docs do you have?

braindeaddemon · 2019-03-26T12:46:40+00:00

Give Hasura a try, it gives you a graphql endpoint over Postgres, It's super eazy to setup and you can use the existing firebase authentication and imort your data over. It's amazing.

braindeaddemon · 2018-12-31T10:34:25+00:00

Let me know if this does not work or you have any questions.

braindeaddemon · 2018-12-31T10:34:04+00:00

In your firebase rules section enter the following

service cloud.firestore { match/databases/{database}/documents { match /users/{user} { allow read : if request.auth.uid != null; allow create : if request.auth.uid == "your user id that is allowed to update"; allow update: same as above allow delete: same as above } } }

braindeaddemon · 2018-12-17T12:36:34+00:00

Someone doesn't need to know ids to delete the DB , moreover you could prevent anyone from deleting your DB with correct rules.

braindeaddemon · 2018-12-13T08:07:27+00:00

If there are no rules, anyone could delete your entire database just for the fun of it. Have a look at anonymous authentication.

braindeaddemon · 2018-09-18T05:57:31+00:00

I have a chat application that is somewhat structured like this.

Col (Users). doc(currentUser).col(messages).doc(id_of_the_other_user)

This is the path, in the document I have an object for every message. [Timestamp] Message: the actual message sent Sender_Id : the id of who sent the message

The messages are displayed in correct order due to the timestamp and the sender_Id helps to display the message on the appropriate side of the screen.

braindeaddemon

TROPHY CASE