Prepare for using oti search from a different server

[jimallman]

The OTOL API makes assumptions about the oti's location and base URL. To match the flexibility elsewhere, we should take advantage of the server-config variables used in install-web2py-apps.sh, preferably using the same OTI_BASE_URL (which of course incorporates the host and port plus leading path information).

I'm putting this ticket here because we'll need to modify oti_search module (or its caller) to use this standard form. It looks very close already, I'm checking now to see if they agree on what the "base URL" means in this case.

[jar398]

I'm OK with assuming OTI and the API run on the same server, if that would
help in any way.
To me they are two parts of the same thing.

On Wed, Jan 29, 2014 at 12:44 PM, Jim Allman notifications@github.comwrote:

The OTOL API makes assumptions about the oti's location and base URL. To
match the flexibility elsewhere, we should take advantage of the
server-config variables used in install-web2py-apps.sh, preferably using
the same OTI_BASE_URL (which of course incorporates the host and port
plus leading path information).

I'm putting this ticket here because we'll need to modify oti_searchmodule (or its caller) to use this standard form. It looks very close
already, I'm checking now to see if they agree on what the "base URL" means
in this case.

Reply to this email directly or view it on GitHubhttps://github.com//issues/48
.

Jonathan A Rees
National Evolutionary Synthesis Center

[jimallman]

Drat, I didn't see your comment. I have this working as described above. (These services are on separate servers in our current Dev setup.)