Page MenuHomePhabricator

Update wikibase-docker configuration for wdqs-frontend
Closed, ResolvedPublic

Description

Reported in wikibase telegram.

I cloned the wikibase-docker repository today and started it up with 'docker-compose -d'. I haven't added any properties or items yet, but when I go to the query service UI on port 8282 and run a query it returns data from Wikidata instead. Is it OK ask about things like this on this channel?

It sounds like the code for the wdqs front-end in terms of where or how things are configured has changed and the code in wikibase-docker doing thsi configuration needs updating.

Event Timeline

Addshore triaged this task as High priority.Jul 1 2019, 8:18 PM
Addshore moved this task from incoming to consider for next sprint on the Wikidata board.
Addshore moved this task from Backlog to Bugs on the Wikibase-Docker-2017+ board.
Addshore added a project: Wikidata-Campsite.
Addshore moved this task from Incoming to Ready to estimate on the Wikidata-Campsite board.

Yes, I replicated this issue on a Wikibase I was installing for a 2-minute demo for the upcoming Wikibase workshop in Ghent. The included wikibase query service is indeed returning results from Wikidata

The issue identified was because the custom-config.json was not overwriting the settings stored in default-config.json. To overcome this a pull request was made that overwrites the default-config.json file upon startup.

See: https://github.com/wmde/wikibase-docker/pull/85

hoo subscribed.

The issue identified was because the custom-config.json was not overwriting the settings stored in default-config.json. To overcome this a pull request was made that overwrites the default-config.json file upon startup.

See: https://github.com/wmde/wikibase-docker/pull/85

If custom-config.json doesn’t override default-config.json, doesn’t that mean the query UI has to be fixed, rather than overriding default-config.json in Docker? The whole point of the separation was that default-config.json doesn’t have to be changed, after all.

So I tested it locally and it doesn't query wikidata anymore but I also feel it's not reading the custom config at all either. Let me double check.

The issue identified was because the custom-config.json was not overwriting the settings stored in default-config.json. To overcome this a pull request was made that overwrites the default-config.json file upon startup.

See: https://github.com/wmde/wikibase-docker/pull/85

If custom-config.json doesn’t override default-config.json, doesn’t that mean the query UI has to be fixed, rather than overriding default-config.json in Docker? The whole point of the separation was that default-config.json doesn’t have to be changed, after all.

No, Let me explain in depth: WDQS GUI checks for existence of custom-config.json on its root directory (see wikibase/config.js) and overrides values of default-config.json if it finds them. The issue with the docker image was that it was put in the wrong directory (See PR and working directory) causing the config.json not to pick up the file. Now that's fixed. (I double checked everything)

I also feel it's not reading the custom config at all either. Let me double check.

I have very misleading feelings, the configs are being picked up, the issue is there's a fatal in JS. I fix that now.

the issue is there's a fatal in JS. I fix that now.

Unbelievable, AdBlock prevented loading UrlShortener.js and that caused fatals. With whitelisting localhost (!) it works like a charm. There's nothing to fix here.

Unbelievable, AdBlock prevented loading UrlShortener.js and that caused fatals. With whitelisting localhost (!) it works like a charm. There's nothing to fix here.

That would be T223068: Wikibase Query Service calls get flagged as tracker calls by some Firefox extensions.