Currently we are using Cassandra as the (only possible) storage back-end for RESTBase in MediaWiki-Vagrant. However, it consumes a lot of user's precious memory and is really not needed for a development set-up. We are working on getting T88191: SQLite3 storage module back-end for RESTBase out of the door, and as soon as it's ready, we can switch to the more lightweight SQLite variant.
Description
Description
Details
Details
| Project | Branch | Lines +/- | Subject | |
|---|---|---|---|---|
| mediawiki/vagrant | master | +130 -28 | Switch RESTBase to use SQLite3 storage |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | • mobrovac | T107447 Switch to SQLite as the RESTBase back-end in MW-Vagrant | |||
| Resolved | • Pchelolo | T88191 SQLite3 storage module back-end for RESTBase | |||
| Resolved | • Pchelolo | T89888 Support 'static' columns in SQLite3 module back-end for RESTBase | |||
| Resolved | • Pchelolo | T103406 move restbase-mod-table-cassandra tests and spec into a separate module | |||
| Resolved | Hardikj | T99696 cleanup and refactor test/index.js |
Event Timeline
Comment Actions
In order to keep the compatibility with Windows hosts which do not allow symlinks out of the box (cf. T100202), we use npm install --no-bin-links. However, the install procedure of the sqlite3 npm package relies on node-pre-gyp having a symlink created in node_modules/.bin, causing the installation to fail:
$ npm install --no-bin-links > sqlite3@3.0.10 install /vagrant/srv/restbase/node_modules/restbase-mod-table-sqlite/node_modules/sqlite3 > node-pre-gyp install --fallback-to-build sh: 1: node-pre-gyp: not found npm WARN This failure might be due to the use of legacy binary "node" npm WARN For further explanations, please read /usr/share/doc/nodejs/README.Debian npm ERR! weird error 127 npm ERR! not ok code 0
Comment Actions
Change 231047 had a related patch set uploaded (by Mobrovac):
Switch RESTBase to use SQLite3 storage