Control the locks through Homematic CCU and CCU-Jack
Find a file
Stefan Bethke 6d3e550914
Some checks failed
docker-image / docker (push) Has been cancelled
Pretty up
2025-05-27 19:28:37 +02:00
.forgejo/workflows Add workflow 2025-05-24 13:03:40 +02:00
hmdooris Pretty up 2025-05-27 19:28:37 +02:00
local-dev/import Getting started 2025-05-21 14:44:29 +02:00
.gitignore Getting started 2025-05-20 22:06:51 +02:00
docker-compose.yaml Getting started 2025-05-21 14:44:29 +02:00
Dockerfile Fix Dockerfile and Python version 2025-05-24 14:21:28 +02:00
poetry.lock Fix Dockerfile and Python version 2025-05-24 14:21:28 +02:00
pyproject.toml Fix Dockerfile and Python version 2025-05-24 14:21:28 +02:00
README.md Getting started 2025-05-21 14:44:29 +02:00

hmdooris - Dooris via HomeMatic

Local Development Setup with Docker Compose

The included docker-compose.yaml will bring up a local Keycloak instance with a preconfigured realm that includes a client that can be used to test the application locally. You can log in to the admin console at http://localhost:8080/admin/master/console/ using "admin"/"admin".

Realm Keycloak: Client hmdooris and User hmdooris

In order for ID Invite to create users, it needs to access the Keycloak REST API with suitable credentials. This is implemented through a client hmdooris in the Keycloak realm, with the client secret XXX, and a username of hmdooris and password geheim.

Realm testing: Client hmdooris and User tony

Keycloak will import the realm export from local-dev/import/testing.json and create a realm testing, including a client and a user.

The client ID is hmdooris and the secret is ´8p21riiYPDEhpgRh2rgRDNu9uWVZ9KRj`.

You can log in to the realm and the application with user tony and password tester.

Updating the testing realm

If you'd like to make changes to the configuration of the testing realm, and have it persist across restarts, you can export the realm. Run this command:

docker compose exec -it keycloak /opt/keycloak/data/import/export.sh