AFAICT this hasn't been done yet?
Description
Description
Details
Details
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Re-use Parsoid Varnishes for citoid too | operations/puppet | production | +25 -0 | |
| Expose citoid through misc-web | operations/puppet | production | +3 -0 |
Revisions and Commits
Revisions and Commits
| rODNS operations-dns | |||
| rODNSe9b39d541a6b Introduce citoid.{eqiad,}.wikimedia.org | |||
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Esanders | T67540 VisualEditor: Automatically convert inserted URLs to readable formatted links | |||
| Resolved | Mvolz | T62768 Cite: Auto-filled references based on destination URL / DOI etc. | |||
| Resolved | • GWicke | T76949 Expose the production citoid service publicly so we can start switching scripts over to use it |
Event Timeline
Comment Actions
Change 178419 had a related patch set uploaded (by Catrope):
Expose citoid through misc-web
Comment Actions
Hello,
So I am a bit unclear on this and the two tasks listed as blocked (T62768 and T67540) did not make it any more clear for me. So here's the question:
We want citoid to be publicly available as an endpoint so that Cite and VisualEditor to directly query it, right ?
I assume, Cite is this: http://www.mediawiki.org/wiki/Extension:Cite in which case I am wondering why a Mediawiki Extension can not query an internal endpoint (namely citoid.svc.eqiad.wmnet). I am not at all familiar with Cite so it might be javascript, served by Cite, that runs on the user's browser that does the querying at which point what this ticket asks make sense.
Same thing goes for VisualEditor, I just want to clarify what/who will be doing the endpoint query. Is the situation different than Cite ? And if yes, how ?
As as side note and since I mentioned javascript, what about same origin policy ? Will that end up being a problem ?
Comment Actions
Citoid !== Cite, they're totally different.
However, Gabriel said he would work on setting up a services Varnish thing as part of setting up RESTbase, and Citoid could hitch a ride on that. So this ticket should have been marked as blocked on services, instead it was marked as blocked on ops by mistake.
Under normal circumstances I would have attended SoS yesterday and would have known to file this correctly, but I wasn't able to make it.
Comment Actions
Change 178419 abandoned by Catrope:
Expose citoid through misc-web
Reason:
Forgot to abandon this. Gabriel said he'd work on caching infra for the entire services cluster, which they need for RESTbase, but which Citoid would then also use once it's done.
Comment Actions
Change 184904 had a related patch set uploaded (by Jforrester):
Re-use Parsoid Varnishes for citoid too