So @bhaugen, one issue with creating a demo front-end that uses the API is that I need a live site to pull data from. I can't create a publically viewable front-end that pulls data from my VM. I might be able to port everything over the Digital Ocean droplet, but before I do that I figured I'd ask. Do you have a test server that I can access through the internet up already?
Do you just need to access the API on the server, or do you need to install the Sensorica/valuenetwork fork on the server?
We have two test sites that we are using now. Both of them are occupied, but one of the groups could get bumped for awhile.
That's if you don't want to install the fork on the server.
Otherwise, we should set up a new one to install the fork. Which I think you all should do eventually anyway.
If you don't need to install the fork on the server, we can deploy the API on nrp.sensorica.co. It doesn't affect anything on the operational system. Although I need to tighten down the permissions a bit for that. Too loose now.
I think I'll just spin up a Digital Ocean Droplet and try to install the Sensorica fork onto it. That will provide a publically available test server. I know the API shouldn't affect existing installations, but I don't like the idea of deploying it on nrp.sensorica.co at this early stage.
I played around a bit more with the API and those Bootstrap templates that Maria found. I may be wrong, but it looks like the API is only allowing read transactions? No write? Is that right?
Basically what I'd like to achieve is default implementation of the model.fetch() call in Backbone. If the DRF. My understanding is that Backbone, Angular, and Ember frameworks all expect the same REST API protocol. If we can get them to work out-of-the-box, it'll maximize the potential for allowing people to quickly create their own front ends around the NRP software.