Evaluate integration of SolrWayback

[anjackson]

Rather than continuing to roll our own search and visualization tool, we should consider adopting SolrWayback and collaborating with the NAS team on it. We could start by making it available as an internal tool, within the W3ACT stack. For this, we need to:

• [x] Dockerise it in a way that allows it to work to our Solr indexes.
• [x] Cope with content_type being either single or multiValued.
• [x] Ensure required configuration options to be overridden from environment variables.
• [x] Tomcat should log the response from the server when calls to Solr fail: add alternative logback config for Docker so logs go to the console not a file.
• [x] Implement HTTP and/or WebHDFS WARC record retrieval back-ends so it can work properly with our WARC store.
• [x] SolrWayback relies on url_norm for many queries, but our older indexes do not contain it. Can we work around this somehow?
• [x] To facilitate automated CI testing, switch to a test WARC as well as test Solr documents, i.e. use consistent records so we can search and replay from the test system.
• [x] Allow WAR name to be overridden on launch, so I can use act#solrwayback and hence get it to deploy in the right place.
• [x] Allow alternative playback engine to be overridden. Added ALT_PLAYBACK_PREFIX env var.
• [x] Also override regex for path as our Solr has name only not full path.
• [x] https://github.com/ukwa/ukwa-warc-server/issues/12
• [x] Adjust SolrWayback so it can be deployed at an alternative path (e.g. /act/solrwayback).

It's possible we can't resolve some of these issues without re-indexing. In which case, this will have to wait.

Notes on public use moved to https://github.com/ukwa/ukwa-services/issues/73

[anjackson]

Now built as ukwa/solrwayback:docker-hub-action for testing. Should be configurable to talk to our Solr and WARC servers, and deployable as part of the W3ACT stack.

[anjackson]

Based on this: https://stackoverflow.com/a/69275528/6689

I have modified the fork of SolrWayback to use relative paths in Vue and it seems to work. Documentation indicates that this feature may not work with history.pushState. See the 'limitations' section of https://cli.vuejs.org/config/#publicpath

[anjackson]

This works well enough to trial so calling this done.