Changes

You'll need at least [http://www.mediawiki.org/wiki/Release_notes/1.23 MediaWiki v1.23]. I personally run This site usually runs the same [http://wwwmost recent version available.mediawikiWe're using {{CURRENTVERSION}} at the moment.org/wiki/Special:Version See what version that they're running on mediawiki.org] (1.24wmf3 [[Userand check yours too for free at https:Freephile|greg//freephile.rundlett]] (org/wikireport See the new [[User talkmw:FreephileRESTBase|talkRESTBase]]) 19:39, 9 May 2014 (UTC))caching proxy system usable by VE 

To install the Visual Editor extension in a Webfaction account, you need to first have node installed and working. You can do this by using the [http://docs.webfaction.com/software/custom.html installer in your webfaction panel] and associating a path with the app for a domain. I chose to install 'node' (which is now it's own one-click install). Once you do that you can [https://freephile.org/node visit the path] you configured for node and you should see the "hello world" app that the installer puts in place. You'll need to stop that app, plus remove the cron job that respawns it. Then, in order to reserve and associate a port for the service, you install another 'app'. You do not need to open this port in the firewall unless you plan to share it with other instances, since HTTP talks to the node server on the backend. (I had to export the PORT, but this is no longer necessary if you configure it in localsettings.js<ref><code>parsoidConfig.serverPort = 8080</code> if you are running MediaWiki-Vagrant</ref>.) Depending on the resource constraints of your hosting package, you may need to limit the number of workers spawned by the Parsoid service. It calculates a number based on the number of processors. For a shared hosting account, this is guaranteed to exceed your RAM or CPU limits, so specify the <code>--num-workers</code> option unless you're running on a dedicated host or VM.

To have it run continuously, you might want to use the 'forever' module, but that is just a node way of monitoring processes. You might want to simply use tools build for the purpose like [[monit]]:

forever node api/server.js --num-workers=2 &</source> The console should print out a list of worker pids, and the port number that the server is listening on. In your web browser, if you visit that path and port (setup in your WebFaction node mapping), you should see the Parsoid web service API message. There is no stop script for a shared host, but you should be able to do something like<source lang="bash">for pid in $(/sbin/pidof `which node`); do kill -9 $pid; done