VisualEditor/Cloud VPS

Guide for managing test instance at http://visualeditor-prototype.wmflabs.org/.

Installation steps

1. Create a MediaWiki-Vagrant instance in Cloud VPS
2. Enable VE:
   1. cd /srv/mediawiki-vagrant
   2. mwvagrant roles enable visualeditor and optionally some more roles:
      • mobilefrontend
      • cite
      • citoid
      • textextracts
      • pageimages
   3. mwvagrant provision
3. Make modifications for RESTBase & Parsoid:
   1. mwvagrant ssh
   2. Replace dev.wiki.local.wmftest.net with visualeditor-prototype.wmflabs.org in the following files:
      1. /etc/apache2/site-confs/devwiki/50-RESTBase-Proxy.conf
      2. /etc/parsoid.localsettings.vagrant.js
      3. /vagrant/srv/restbase/config.vagrant.yaml
      4. /vagrant/settings.d/wikis/wiki/settings.d/puppet-managed/00-RESTBase-VRS.php
      5. /vagrant/settings.d/wikis/wiki/settings.d/puppet-managed/05-RESTBase-VisualEditor.php
      6. /vagrant/settings.d/wikis/wiki/settings.d/puppet-managed/10-Citoid.php
   3. If you get a "No wiki found" error, you just need to restart apache (sudo service apache2 restart from within vagrant).

NPM problems

If npm i crashes with "killed", then you can run it from the host:

1. sudo su mwvagrant
2. bash
3. Install nvm
4. nvm install 6.16.0 (or whatever the version is inside vagrant; node -v)
5. npm i

Updating code

Just use mwvagrant git-update. If you enable a new vagrant role and need to provision vagrant, you will need to repeat step 3 from the installation process.

If you reload vagrant, you may need to repeat step 3.3.

Checking out a patch

SSH in to visualeditor-prototype.eqiad.wmflabs, mwvagrant ssh, then use git-review as you would on your local machine.

Differences from live

Some extensions are not installed/configured yet:

• Math
• BetaFeatures
• Kartographer
• Score
• wikihiero
• ...