It was decided to replace the legacy application “Schöffenverwaltung”, which was used by the District Administration Department until 2024, with a MAKE application based on the it@M reference architecture. The requirement that the specialist procedure can supports the application for the office of lay judge and honorary judges at the Administrative Court without a change request will be taken into account. This new application is referred to as “Ehrenamtjustiz”. The application Ehrenamtjustiz supports the clerk in the District Administration Department in recording and managing applicants, resolving conflicts in the residents' registration data and drawing up the list of proposals for lay judge and honorary judges at the Administrative Court . Citizens can also apply for aldermen online.
Ehrenamtsjustiz based on the RefArch (reference architecture) of it@M.
To learn more about the architecture itself, checkout its documentation or code.
The templates are based on Spring and Vue.js.
The project is built with technologies we use in our projects (reference architecture):
mkdir ~/develop
cd ~/develop
git clone https://github.com/it-at-m/ehrenamt-justiz.git
cd ehrenamt-justiz
Manually adjust the source entrypoint.sh (~/develop\ehrenamt-justiz\ehrenamt-justiz-eai\entrypoint.sh)
Details can be found in the documentation here:
ehrenamt-justiz/ehrenamt-justiz-eai/entrypoint.sh
Manually adjust the user and password in docker-compose.yml (~\develop\ehrenamt-justiz\stack\docker-compose.yml) for calling the EAI:
eai:
...
environment:
- PRODUCER_USER=
- PRODUCER_PASSWORD=
The following must be done to use the EJ change service (Kafka)
- Copy kafka-auth-keystore.jks and truststore.jks (Can be found in Keystore for Ehrenamt-Justiz) to folder ~/develop/ehrenamt-justiz/ehrenamt-justiz-aenderungsservice/src/main/resources
- Manually add the user and password in ~/develop/ehrenamt-justiz/stack/docker-compose.yml (User and password can be found in Keystore for Ehrenamt-Justiz)
services: ... aenderungsservice: ... environment: ... - KEY_STORE_PASSWORD= - TRUST_STORE_PASSWORD= - Manually set the GROUP_ID (The Group ID identifies a group of consumer instances that jointly consume messages from one or more Kafka topics) in ~/develop/ehrenamt-justiz/stack/docker-compose.yml for kafka.
services: ... aenderungsservice: ... environment: ... - GROUP_ID=lhm-ewo-eai-aenderungen-ehrenamt-justiz...
cd ~/develop/ehrenamt-justiz/stack
podman compose --profile=backend --profile=frontend --profile=eai --profile=online --profile=aenderungsservice up -d
These containers are started:
url: http://localhost:8083
These users are only for testing purpose in podman:
| user | Description | role | password |
|---|---|---|---|
| nosach | normal user with basic rights | clientrole_sachbearbeiter | nosach |
| sosach | users with extended rights | clientrole_sondersachbearbeiter | sosach |
| soadmin | administrator rights | clientrole_administrator | soadmin |
After starting the application for the first time, an active configuration must first be created. All data is saved under this configuration.
url: http://localhost:8083/public/online/
podman compose --profile=backend --profile=frontend --profile=eai --profile=online --profile=aenderungsservice stop
- Open action for api release: API release
- Click on "view runs"
- Click on "run workflow"
- Select branch, module to release (ehrenamtjustiz-api), release version (e.g. 1.0.0) and next version to use after release (e.g. 1.0.1-SNAPSHOT)
- Click on "Run workflow"
- Check running action
- Releases saved in the central Maven repository. Wait, wait and wait until it is there.
- Update api-versions in pom.xml in backend and aenderungsservice and eai and build releases
- Open action for maven release: Maven release workflow
- Click on "view runs"
- Click on "run workflow"
- Select branch, version to use when preparing a release (e.g. 0.0.4) and version to use for new local working copy (e.g. 0.0.5-SNAPSHOT) and Service-Name (ehrenamt-justiz-backend, ehrenamt-justiz-eai or ehrenamt-justiz-aenderungsservice)
- Click on "Run workflow"
- Check running action
- Release can be found here: Releases
- Update versions in docker-compose.yml for podman
- Open action for npm release: npm release workflow
- Click on "view runs"
- Click on "run workflow"
- Select branch, version increment type (patch, minor or major) and node service to release
- Click on "Run workflow"
- Check running action
- Release can be found here: Releases
- Update versions in docker-compose.yml for podman
Contributions are what make the open source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated.
If you have a suggestion that would make this better, please open an issue and fill out the appropriate issue form with as much information as possible. If you want to work on a solution, fork the repo and create a pull request. Don't forget to give the project a star! Thanks again!
More about this in the CODE_OF_CONDUCT file.
Distributed under the MIT License. See LICENSE file for more information.
it@M - opensource@muenchen.de