On 01/27/2015 11:46 AM, C. Scott Ananian wrote:
We already run a public Parsoid service.
But, this doesn't serve wiki content from wikis other than wikimedia
wikis and we are unlikely to do so with the existing production WMF cluster.
The discussion is whether we should / will run a different cluster for
smallish wikis.
Subbu.
Kiwix uses it, as does Nell's Wikipedia. I believe some non-WMF content
translation efforts also use it.
Usage limits and API keys would probably be a reasonable thing to do,
longer-term.
--scott
On Tue, Jan 27, 2015 at 11:20 AM, Brion Vibber <[email protected]>
wrote:
On Tue, Jan 27, 2015 at 11:10 AM, James Forrester <
[email protected]>
wrote:
On 27 January 2015 at 11:04, Brion Vibber <[email protected]> wrote:
Whether this can apply also to things like Parsoid might be tricky --
that's the biggest Scary Thing since core editing with VE/Flow is going
to
depend on it.
​Running Parsoid as a public service (with some soft-ish API limits)
would
allow us to support the oft-cited user who has a dumb PHP-only box and no
means to install a node service, so that has my support;
Yay!
however, I worry
that WMF might not be the best organisation to provide this if people
wanted it at large for commercial use.
Agreed... but if not us, then who?
/me looks around at folks, wonders if anyone wants to commit to running
such a service as a third-party that we could make super-easy for shared
PHP-host users to use...
-- brion
_______________________________________________
Wikitech-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
_______________________________________________
Wikitech-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
