fix redpanda and registry

docker-compose.yml

@@ -0,0 +1,87 @@
+name: infinimotion
+networks:
+  backend_network:
+    driver: bridge
+  redpanda_network:
+    driver: bridge
+services:
+  backend:
+    image: git.infinimotion.de/infinimotion/backend:latest
+    container_name: backend
+    networks:
+      - backend_network
+      - redpanda_network
+    depends_on:
+      - redpanda-0
+    #environment:
+    #  KAFKA_SECURITY_PROTOCOL: "SASL_PLAINTEXT"
+    #  KAFKA_SASL_MECHANISM: "SCRAM-SHA-256"
+    #  KAFKA_SASL_JAAS_CONFIG: 'org.apache.kafka.common.security.scram.ScramLoginModule required username="im-admin" password="a552855c0d842e90895121cf614c31f950086cab";'
+    #ports:
+    #  - 8080:8080
+  redpanda-0:
+    command:
+      - redpanda
+      - start
+      - --kafka-addr internal://0.0.0.0:9092,external://0.0.0.0:19092
+      # Address the broker advertises to clients that connect to the Kafka API.
+      # Use the internal addresses to connect to the Redpanda brokers'
+      # from inside the same Docker network.
+      # Use the external addresses to connect to the Redpanda brokers'
+      # from outside the Docker network.
+      - --advertise-kafka-addr internal://redpanda-0:9092,external://localhost:19092
+      - --pandaproxy-addr internal://0.0.0.0:8082,external://0.0.0.0:18082
+      # Address the broker advertises to clients that connect to the HTTP Proxy.
+      - --advertise-pandaproxy-addr internal://redpanda-0:8082,external://localhost:18082
+      - --schema-registry-addr internal://0.0.0.0:8081,external://0.0.0.0:18081
+      # Redpanda brokers use the RPC API to communicate with each other internally.
+      - --rpc-addr redpanda-0:33145
+      - --advertise-rpc-addr redpanda-0:33145
+      # Mode dev-container uses well-known configuration properties for development in containers.
+      - --mode dev-container
+      # Tells Seastar (the framework Redpanda uses under the hood) to use 1 core on the system.
+      - --smp 1
+      - --default-log-level=info
+    image: docker.redpanda.com/redpandadata/redpanda:v25.2.9
+    container_name: redpanda-0
+    environment:
+      RP_BOOTSTRAP_USER: "im-admin:a552855c0d842e90895121cf614c31f950086cab"
+    volumes:
+      - ./redpanda/redpanda-0:/var/lib/redpanda/data
+      - ./redpanda/bootstrap.yml:/etc/redpanda/.bootstrap.yaml
+    networks:
+      - redpanda_network
+    ports:
+      #      - 18081:18081
+      #      - 18082:18082
+      - 19092:19092
+  #      - 19644:9644
+  console:
+    container_name: redpanda-console
+    image: docker.redpanda.com/redpandadata/console:v3.2.2
+    networks:
+      - redpanda_network
+    entrypoint: /bin/sh
+    command: -c 'echo "$$CONSOLE_CONFIG_FILE" > /tmp/config.yml; /app/console'
+    environment:
+      CONFIG_FILEPATH: /tmp/config.yml
+      CONSOLE_CONFIG_FILE: |
+        kafka:
+          brokers: ["redpanda-0:9092"]
+          sasl:
+            enabled: true
+            username: im-admin
+            password: a552855c0d842e90895121cf614c31f950086cab
+            mechanism: SCRAM-SHA-256
+        schemaRegistry:
+          enabled: true
+          urls: ["http://redpanda-0:8081"]
+        redpanda:
+          adminApi:
+            enabled: true
+            urls: ["http://redpanda-0:9644"]
+    ports:
+      - "127.0.0.1:8086:8080"
+    # nur lokal, weil nicht authentifiziert (enterprise feature...)
+    depends_on:
+      - redpanda-0