Tracker bug for things that need to be done before RESTBase can be relied on in production, primarily by VE.
- Mentioned In
- T91661: Have a RESTbase vagrant role
T91533: Services team Q3 (Jan - March 2015) quarterly goal tracking
T90304: Load HTML in parallel with JSON metadata
T1228: RESTbase deployment
- Mentioned Here
- T87520: Set up update jobs for RESTBase: code done and deployed, to be configured
T89066: Parsoid performance: Use RESTBase from the MediaWiki Virtual Rest Service on group1/group2 wikis
T88016: Handle read access for private wikis
@greg, we're good, it's out :) We're currently testing some more T87520 , but all of the things have been successfully deployed. Job updates are working for the most part, as well the integration with VE. We're currently testing them on testwiki, but plan to expand to group0 these days. So you can cross RESTBase off of your list!
The remaining blocking tasks should be thought of as reminders rather than blockers.
We are still finishing up some things (notably expanding change tracking to all wikis along with switching VE over on more wikis), but the primary roll-out has certainly happened. VE has been working great out of the box using RESTBase on https://test.wikipedia.org/.
The remaining tasks are being finished up / worked on. We can re-parent them & close this task if you prefer.
As of now RESTBase
- has the latest revisions of all wikipedias and phase0 wikis,
- processes updates from those wikis, and
- is successfully used by VisualEditor on all phase0 wikis.
This means that RESTBase is now in production, and we can close this ticket.
The follow-up tasks for further monitoring improvements and beta labs testing will be addressed separately.