While I was exploring Google Cloud Platform, I immediately followed some links to Firebase, a Google product that acts as a quick and highly available backend for many apps.
One quick way to experiment with this is to store most of the settings on the "/settings" route in Firebase. Certain important credentials maybe shouldn't be stored here but defaults for keys in the data table and whether you show or hide the stats search on load are safe to try.
Since it is a Google product, using a Google account should be easy to set up and all CU employees have Google accounts.
While I was exploring Google Cloud Platform, I immediately followed some links to Firebase, a Google product that acts as a quick and highly available backend for many apps.
https://firebase.google.com/
One quick way to experiment with this is to store most of the settings on the "/settings" route in Firebase. Certain important credentials maybe shouldn't be stored here but defaults for keys in the data table and whether you show or hide the stats search on load are safe to try.
Since it is a Google product, using a Google account should be easy to set up and all CU employees have Google accounts.