RIS Search

These instructions are written assuming development takes place on macOS.

Prerequisites

Java

This project uses Java 21 for the backend. Check your java version with

java --version

If java is not installed, install it

brew install openjdk@21

and check the version again. If the version returned is not 21, you may need to change your version

sudo ln -sfn /opt/homebrew/opt/openjdk@21/libexec/openjdk.jdk /Library/Java/JavaVirtualMachines/openjdk-21.jdk
echo 'export PATH="/opt/homebrew/opt/openjdk@21/bin:$PATH"' >> ~/.zshrc

Close your shell, open a new one and check the version again.

If you get an error message, try running

brew info java

and follow the steps provided.

Docker

This project uses Docker to run some containers locally. These include

• OpenSearch
• OpenSearch Dashboards
• Keycloak
• Application containers (backend and frontend)

Check Docker is installed by running

docker --version

If docker is not installed, run this to install it.

brew install --cask docker

Make sure to open docker once to complete the installation and start the docker daemon.

Node Talisman

For the provided Git hooks you will need:

brew install lefthook node talisman

Getting started

Clone Repository:

git clone [email protected]:digitalservicebund/ris-search.git
cd ris-search

Run initialization script:

./run.sh init

This will replace placeholders in the application template and install a couple of Git hooks.

Starting Docker

Run

docker-compose up

to start docker.

You will find the following services served at the following addresses:

• OpenSearch running at localhost:9200
• OpenSearch Dashboards at localhost:5601 by default.
• Backend running at localhost:8090
• Frontend running at localhost:3001
• Swagger API documentation for Backend endpoints at localhost:8090/swagger-ui or localhost:3000/api/docs/index.html.

Backend

Build and run

If you don't want to use Docker for running the backend, you can build and run the application backend with:

cd backend
./gradlew bootRun

The API application will be available at localhost:8090.

Test

The project has distinct unit and integration test sets.

To run just the unit tests:

./gradlew test

To run the integration tests:

./gradlew integrationTest

Note: Running integration tests requires passing unit tests (in Gradle terms: integration tests depend on unit tests), so unit tests are going to be run first. In case there are failing unit tests we won't attempt to continue running any integration tests.

To run integration tests exclusively, without the unit test dependency:

./gradlew integrationTest --exclude-task test

Denoting an integration test is accomplished by using a JUnit 5 tag annotation: @Tag("integration").

Furthermore, there is another type of test worth mentioning. We're using ArchUnit for ensuring certain architectural characteristics, for instance making sure that there are no cyclic dependencies.

Frontend

To run the frontend, see ./frontend/README.md

End-to-end tests

The end-to-end tests use Playwright. The test cases are located in the frontend/e2e directory.

Setup

Install the required browser dependencies by running

npx playwright install --with-deps chromium

Running using Docker

To run the end-to-end tests, run e.g.

docker compose -f docker-compose-ci.yml up -d
npx playwright test --project chromium
docker compose down

Running locally

To run the end-to-end tests against the local environment, start just the required dependencies:

docker compose -f docker-compose-ci.yml up -d opensearch keycloak

The backend should be started with profiles e2e and default, e.g., by setting SPRING_PROFILES_ACTIVE=e2e,default. This will ensure that the end-to-end data sample and OpenSearch indices will be used, ignoring any other data in OpenSearch.

The frontend can be started normally.

Running Playwright

You may execute the end-to-end tests by running yarn run e2e, or yarn run e2e -- --ui to view them in a browser.

If using the VS Code extension for Playwright, make sure to select the "setup" project. Otherwise, the authentication flow will not be run prior to executing the tests.

Content

• Commands
• Container image
• Vulnerability Scanning
• Dump caselaw data to OpenSearch

Architecture Decision Records

Architecture decisions are kept in the doc/adr directory. For adding new records install the adr-tools package:

brew install adr-tools

See https://github.com/npryce/adr-tools regarding usage.

About the Repository

Program Name: NeuRIS (Neues Rechtsinformationsportal)
Description: An intuitive legal information system aimed at simplifying access to laws, regulations, and court decisions in Germany.

Copyright (C) 2025 DigitalService GmbH des Bundes

Author's Contact Information

DigitalService GmbH des Bundes
Prinzessinnenstraße 8-14,
10969 Berlin, Germany
Email: [email protected]
Website: https://digitalservice.bund.de

Contributing

🇬🇧 Currently the repository has data that can not be publicly released and is private. We plan to remove the repository history and make it public. Until then, everyone inside DigitalService is welcome to contribute to the development of the ris-search. You can contribute by opening pull request, providing documentation or answering questions or giving feedback. Please always follow the guidelines and our Code of Conduct.

🇩🇪 Derzeit enthält das Repository Daten, die nicht öffentlich zugänglich gemacht werden können, und ist daher privat. Wir planen, die Repository-Historie zu entfernen und es öffentlich zugänglich zu machen. Bis dahin sind alle Mitarbeitenden von DigitalService herzlich eingeladen, zur Entwicklung der ris-search beizutragen. Du kannst beitragen, indem du Pull Requests erstellst, Dokumentation bereitstellst oder Fragen beantwortest bzw. Feedback gibst. Bitte befolge immer die Richtlinien und unseren Verhaltenskodex.

Contributing code

🇬🇧 Open a pull request with your changes and it will be reviewed by someone from the team. When you submit a pull request, you declare that you have the right to license your contribution to the DigitalService and the community. By submitting the patch, you agree that your contributions are licensed under the MIT license.

Please make sure that your changes have been tested before submitting a pull request.

🇩🇪 Nach dem Erstellen eines Pull Requests wird dieser von einer Person aus dem Team überprüft. Wenn du einen Pull Request einreichst, erklärst du dich damit einverstanden, deinen Beitrag an den DigitalService und die Community zu lizenzieren. Durch das Einreichen des Patches erklärst du dich damit einverstanden, dass deine Beiträge unter der MIT-Lizenz lizenziert sind.

Bitte stelle sicher, dass deine Änderungen getestet wurden, bevor du einen Pull Request sendest.