status-im/burnchart
2
0
Fork 0
mirror of https://github.com/status-im/burnchart.git synced 2025-01-27 10:54:59 +00:00
Code Issues Projects Releases Wiki Activity

how to deal with subscribers notes

Browse Source
This commit is contained in:
Radek Stepan 2014-09-09 20:47:52 -07:00
parent 3b69fd6d4b
commit c520aa6f28
1 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
NOTES.md
View File

@ -196,6 +196,8 @@ Using a free instance of [IronWorker](http://dev.iron.io/worker/reference/enviro
Because security rules cannot override existing rules, we need to separate the table of subscribers from saving the info on the suer herself. Because security rules cannot override existing rules, we need to separate the table of subscribers from saving the info on the suer herself.
- [ ] fetch updates for a `private` repo only if our user is in a `subscribers` collection which is not writable by them - [ ] fetch updates for a `private` repo only if our user has a `plan` flag set to `business` or whatever
- [ ] use a JS library to allow Stripe payment processing; people submit their card details and we get a Stripe `token` back. Save this token and user id on FB under `payments` collection. - [ ] use a JS library to allow Stripe payment processing; people submit their card details and we get a Stripe `token` back. Save this token and user id on FB under `payments` collection that only adds new entries, never deletes.
- [ ] have a worker process the `payments` and write into `subscribers` with our own `admin_key` - [ ] have a worker process the `payments` ever 6 minutes or faster via IronWorker
- [ ] run an extra worker to check for for repos that return 404 when user is on an `open-source` plan; this is to find cheaters
- [ ] run an extra worker that checks for `business` plans and if we have payments for these or not