Open egonw opened 7 years ago
Nuno, related, will this have a "Swagger" API you? Can we integrate with the live docs of the non-IRI-based webservice APIs?
@egonw what do you mean? I can adapt the one from bridgedb. Is that it?
there's not many operations in IMS web service, so it should be easy enough to make a swagger file for it.
On 5 December 2016 at 08:53, nunogit notifications@github.com wrote:
@egonw https://github.com/egonw what do you mean? I can adapt the one from bridgedb. Is that what you mean?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/bridgedb/BridgeDb/issues/37#issuecomment-264798324, or mute the thread https://github.com/notifications/unsubscribe-auth/AAPd5VQgZyO7Ko3fue521RCFSOOpj1sUks5rE9EfgaJpZM4LDlQ_ .
-- Stian Soiland-Reyes, eScience Lab School of Computer Science The University of Manchester http://orcid.org/0000-0001-9842-9718
I can help dockerize it, it should be pretty similar to the augmented Open PHACTS install.
Where could we host it? Would one of the free cloud services work? It needs a mySQL server and a servlet container for the WAR (e.g. Tomcat or Jetty).
ye old openphacts.cs.man.ac.uk
could do it, but seems to have died..
http://beta.openphacts.org:3004/QueryExpander/BridgeDbApi is publicly accessible and could work if we just got a https:// proxy without :3004
somewhere.
Not sure if it being public is intentional (TODO Stian: check with D2Discovery folks), but it should work well as that is used by the backend of the Open PHACTS API.
Similarly we have http://heater.cs.man.ac.uk:3004/QueryExpander/BridgeDbApi which I have not put any uptime warranties on.
Both of these are however with the Open PHACTS augmented set of services like the Query expander and lenses.
I have reinstalled openphacts.cs.man.ac.uk
with Ubuntu 16.04 (sad shutting it down with update 2100 days! ) now seting up IMS with Docker and the 2.1 linksets.
It would look just like http://openphacts.cs.man.ac.uk:3004/QueryExpander/ (bar the funny ports) -- or is it a different web service you want to deploy?
@stain -- http://beta.openphacts.org:3004/ wasn't public by design, but found it useful to use it occasionally so have intentionally not shut it down, at least not yet.
Regarding URLs, what URLs ideally would redirect to beta:3004? Or for that matter, is there a master list somewhere of all the Open PHACTS URLs that ought to point to something?
With a public version of the IMS web services developed in Open PHACTS.