Guest User

Untitled

a guest
Oct 22nd, 2017
80
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 0.93 KB | None | 0 0
  1. New flightboard project based on latest boilerplate
  2.  
  3. Create way to generically store all activities (Data will be poured in from several APIs)
  4. We need to distill the information down to universal bits
  5. Pivotal
  6. Gitorious (Or just git)
  7. In-House Invoicing App
  8. Etc
  9. Note that pulling from each of these APIs will be unique, so it might make sense to write a daemon for each individual api worker
  10.  
  11. Background processes should pull from the external APIs, inserting new data into our database
  12.  
  13. On the client side (The flight board itself), we can either:
  14. A) Poll for new data
  15. B) Have websockets open that listen for updates
  16. If we go this route, Juggernaut is a good candidate. Just write an after_create hook to push out the data.
  17.  
  18. There's some design for this thing kicking around somewhere. Using that we can disable the parts we're not engineering, but
  19. keep the space for them, allowing for a pretty complete markup.
Add Comment
Please, Sign In to add comment