This is a task that we'll likely need to figure out as we are trying to figure out what approach to take.
From the email discussions, it sounds like Tulsa courtbot is able to call an remote API to get court data (that we'll provide), to allow reuse.
If we do need to host a service, it would be best if we are using a common approach that Code for San Jose uses to host services (as services do have a cost associated with it). We'll need a place to deploy REST services (a server), and a place to deploy a database.
Task:
[ ] Determine the options that are available within Court for San Jose to host server that provides REST API endpoint.
[ ] Determine the options that are available for a database.
This is a task that we'll likely need to figure out as we are trying to figure out what approach to take. From the email discussions, it sounds like Tulsa courtbot is able to call an remote API to get court data (that we'll provide), to allow reuse.
If we do need to host a service, it would be best if we are using a common approach that Code for San Jose uses to host services (as services do have a cost associated with it). We'll need a place to deploy REST services (a server), and a place to deploy a database.
Task: