hackthenorth / mobile-backend Goto Github PK

@hackthenorth/commiters @snario

The code I've written to write updates to Firebase and send off notifications to users via GCM is mostly finished, except for a few TODOs for GCM and the fact that we don't have automated tests yet.

It'd be sweet if someone could read it over. Any feedback is welcome, but mostly I just want to make sure that there isn't anything that doesn't make sense, even if you don't know how GCM works.

@KartikTalwar

Here's a breakdown of the schema as I see it:

/mobile/gcm

• Just a list of strings:

{
  "abc123": "dummy",
  "def456": "dummy", ...
}

• Public writes (set it to disallow deleting though)
• Secret-only reads

/mobile/mentors, /mobile/team, /mobile/updates, /mobile/schedule, /mobile/prizes

• List of objects as specified here
• Public reads
• Secret-only writes

/mobile/test

• just a string:

"DO NOT DELETE; used for testing"

• Secret-reads and writes
• used for testing the scripts

So, the GCM API key that we're given only works for whitelisted IP addresses. So, like, we have to add every admin's IP address to the whitelist, and if they move and get a new IP then it'll break. Depending on how much you value things just working and how many admins we have using these scripts, this can just be a minor annoyance, or something that we have to fix. If we only have one or two people using these scripts it's probably not worth the effort to set something up, they'll just have to log in to the dashboard and add their ip.

In case it's something we have to fix, I'm trying to think of a way to let people use this script without having to add their IP address to the GCM whitelist. If we had a canonical admin computer that is accessible via ssh or something, then we can just have everyone run the scripts via ssh or something. I think we might be able to get something like this from the CSC.

Anyway, if anyone else has any ideas, that'd be great.