This page describes the technical setup of the FactGrid website and services.
MediaWiki is installed under
/var/www/ as document root,
with the standard MediaWiki short URL setup to rewrite
The git repositories for quickstatements and its dependency magnustools are cloned under
and symlinks in
/var/www/ point into their
There is an
oauth.ini configuration file in
(for this consumer,
with a request modeled after the original Wikidata consumer),
config.json file in
/src/quickstatements/public_html/ describes the URL layout of the FactGrid site
and selects FactGrid as the site to use.
Logs go to
The bot has not been set up yet, so “run in background” doesn’t currently work.
The query service source is cloned in
built using ant as described in the “getting started” document,
and unzipped into
/srv/wdqs/ is a symlink).
RWStore.properties is edited to adjust the location of the journal file,
which we have in
There is also a nearly-empty
mwservices.conf file (
to avoid a warning if that file is missing completely.
The query service itself runs as the
blazegraph.service systemd unit
systemctl cat blazegraph to see the configuration files).
Its standard output and error go to the journal,
and can be viewed by administrators with
journalctl -u blazegraph (add
-e for the latest messages).
The updater for the query service,
which reads updates from the wiki’s recent changes and applies them to the query service,
similarly runs as
The query service UI is cloned in
It can be built using
npm run build,
and the resulting
build/ directory is then copied into
with a symlink
/var/www/query pointing to the latest version.
A few of the files in the repository have uncommitted changes specific to FactGrid;
before updating the GUI, they have to be stashed away.
git stash save && git pull && git stash pop && npm run build && now=$(date -Iseconds) && cp -a build/ /var/www/query-"$now" && ln -sfT query-"$now" /var/www/query # atomically update symlink # optional: remove the old /var/www/query-* directory