pbartusch

Thank you , @gunnarbusch , for highlighting the dependency to the end-to-end test. I see there should be no dependency from an (deployment relevant) end-to-end test towards an example docker-compose...

I think, you describe the SQLite option for SMUI that is already in place. Anyway, persistence with a suitable SLA would need to be established around this database file. From...

Ideation with @mkr : * Goal: create a (breaking) new SMUI major with a reset for the DB structure (beginning with a new 1.sql) * Step forward - options: *...

This issue would also enable the feature requested with PR #66. #66 will be closed for now (for the same reasons #67 was closed). fyi: @epugh

I deactivated the test suite in order to temporarily get the deployment running again, but the test needs to get fixed soon.

Hi, thanks so much for your input. I see some common themes: @renekrie : > A query might trigger more than one rule Is what I meant here with: >...

> I think the information should all be there to do something like that. We make use of the [querqy info logging feature](https://docs.querqy.org/querqy/logging-and-debugging-rewriters.html#info-logging) to segment queries that triggered a rule...

Side note regarding this topic: Some time ago there was a discussion around #86 , also incl. you, @dobestler. Was the idea for this PR also motivated by the idea...

Let me try to conclude to get a nice concept eventually: The primary motivation for this feature is to enable Search Managers to immediately see the impact of rules while...

**The major goal of this story is to:** * Refactor the deployment part of SMUI, so that the complexity of 2nd search engine (Elasticsearch) supported, can be handled & maintained...