You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
now that we have an API, maybe host the roster on the server and have the clients check for and download it. Would need to have some timestamp on each one, and clients could compare, and tell the host which roster they used. Also allow multiple rosters (for different agencies).
This is working - Steve added the script on the server that grabs the roster from D4H once a day and saves it in the 'roster' table of SignIn.db, and a corresponding API call was added so nodes can grab the latest roster from the cloud server then save it as a local .json file; on each node, the node only actually uses roster data from the .json file.
Remaining items to clean up before closing this ticket:
show the node admin what the date of the json file is, i.e. when it was grabbed from the cloud server, and also show the number of entries or such
add inline docs and header in the cloud server script and include it in the repo (do we want a separate repo only for the server? probably so! In that case push.py could be in that repo too)
The text was updated successfully, but these errors were encountered: