Another possibility is to shell out to nodejs-based services as an
alternative to running them as ongoing web services.
This may not be super performant, but it should work -- just as we've been
able to shell out to system binaries, Python scripts, ocaml, lua, etc for
years. Would require having node *present* on the system but wouldn't
require running a web service.
Something to consider trying...
-- brion
On Tue, Jan 27, 2015 at 11:20 AM, Brion Vibber <bvibber(a)wikimedia.org>
wrote:
On Tue, Jan 27, 2015 at 11:10 AM, James Forrester
<
jforrester(a)wikimedia.org> wrote:
On 27 January 2015 at 11:04, Brion Vibber
<bvibber(a)wikimedia.org> 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