0.38.0 - Major doc update, bugfixes and UI improvements

Content

This week's release is the occasion for us to propose a long overdue rewritten deployment documentation.
You will find it in the https://github.com/checkmarble/marble/tree/main/installation folder.
With this, we tried to give a more step-by-step guide on configuring Marble, making the configuration files more readable, removing ambiguity of the format expected by some configuration elements, and generally make it much easier to self-host Marble.

We released some other feature improvements and bug fixes:

Improvements

• sanction check matches display links to the wikidata page of entities
• sanction check match details correctly break lines for non latin text
• sanction check configuration trigger condition is now options, like the scenario level trigger condition
• test run statistics are computed in the background automatically, for a much faster display in the app

Bug fixes

• test run statistics by decision outcome were wrong in some cases
• test runs are now correctly limited to one active per scenario, not one per organization
• batch (scheduled) execution of scenarios was not working for scenarios with an empty trigger condition (last week's release)

Deployment instructions

Warning

Change in the required environment variables to run the Marble application

Some environment variables expected by the backend and frontend containers for the Marble app have changed. The detail is below:

1. Frontend environment
   • MARBLE_API_DOMAIN_CLIENT renamed to MARBLE_API_URL_CLIENT (format unchanged)
   • MARBLE_API_DOMAIN_SERVER renamed to MARBLE_API_URL_SERVER (format unchanged)
   • MARBLE_APP_DOMAIN renamed to MARBLE_APP_URL (format unchanged)
2. Backend environment
   • MARBLE_APP_HOST renamed to MARBLE_APP_URL. Format was a host name (host + port, e.g. localhost:3000), is replaced by a proper url (e.g. http://localhost:3000) to take the same format at the environment variable with the same name on the frontend
   • the scheme (http/https) used for CORS was based on the value of the ENV environment variable (http if development, https otherwise), now directly uses the value of MARBLE_APP_URL => no impact expecter for customers in a production environment

Make sure to modify the values passed to your binary or container (or start by adding the new ones if you are not running with docker compose) before you upgrade to version 0.38.
We apologize for the added complexity of this release, but this evolution should make Marble easier to configure in the long run by reducing ambiguity.