Parsoid/Setup/RESTBase

This page documents how to configure RESTBase to point at a local Parsoid instance.

This is intended for developers only. This does not describe production configuration of RESTBase.

Setting up a RESTBase storage backend
First you will need to set up a storage backend for RESTBase. When that is done, you'll need to configure RESTBase, Parsoid, and Visual Editor to point at each other.

Typical small installations
If you aren't Wikipedia, we recommend that you use the SQLite backend. Installation for that is described at https://github.com/wikimedia/restbase-mod-table-sqlite.

Large installations
Large installations can use Cassandra for scalable storage.

Tweaking Cassandra for testing
RESTBase can use Cassandra for backend storage. However, the default configuration of Cassandra (on Debian, at least) is more suited for production than local development. For example, Cassandra's default configuration attempts to consume between 800M and 4G of memory for its heap, which can be a substantial fraction of total memory available on a developer's local machine.

After installing Cassandra, I recommend making the following configuration changes to reduce its memory footprint.

Add the following to : (There are probably already commented-out lines in  defining these; uncomment the lines and tweak the values.)

Make the following changes to :

Pointing RESTBase at a local Parsoid
Checkout RESTBase and copy  to   inside the restbase directory, if you have not already done so.

Null

Configuring VisualEditor
Configuring VisualEditor to point to your local RESTBase is easy!

Add the following to your : And, optionally, for direct access to the RESTBase server from client-side code: Note that the portion before  should match the "domain" used above.