-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change CTS to use REST API #257
Comments
The REST API currently seems broken, but I'm watching an issue and will take a crack at this when the API is working again. https://bitbucket.org/fiehnlab/ctsproxy/issues/24/ssl-certificate-has-expired-for-rest-api |
Could |
If it's an easy change, then it might be a good stopgap measure until CTS gets fixed. |
Ok, then I'll jump in on this one. |
I am closing this issue as REST API would still be nice, but CTS seems to be working fine so I'll just mark it as low priority. |
REST API seems to be working now! Features available by REST that are not currently in
|
While puzzling through some problems with
cts_*()
functions (see #255, #243 ) I noticed that CTS has a REST API that is not currently implemented in thects_*()
functions.https://cts.fiehnlab.ucdavis.edu/services
The text was updated successfully, but these errors were encountered: