Skip to content

feat: single edc setup - #3

Open
simon-malok-materna wants to merge 1 commit into
project-construct-x:mainfrom
simon-malok-materna:feat/single-node-docker
Open

feat: single edc setup#3
simon-malok-materna wants to merge 1 commit into
project-construct-x:mainfrom
simon-malok-materna:feat/single-node-docker

Conversation

@simon-malok-materna

Copy link
Copy Markdown

WHAT

  • Added two Docker Compose configurations:
    • in-memory setup
    • persistent setup
  • Added a Traefik reverse proxy for domain-based access
  • Added and updated Bruno collection

WHY

Enable single EDC usage locally.

FURTHER NOTES

The Docker Compose setup is based on an existing configuration that includes both provider and consumer components, but has been adapted for a single EDC instance. It is based on this local setup.

Closes # <-- CXAP4-237

@MarioH91
MarioH91 requested a review from gostev-p August 5, 2026 09:23

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Diese Datei wird nirgendswo verwendet, zumindest, wenn ich die Anwendungen über die Docker-Compose starte. Überprüft bitte nochmal, ob ihr diese Datei braucht.

Comment on lines +64 to +84
vault-init:
container_name: vault-init
image: alpine:3.19
depends_on:
shared-vault:
condition: service_healthy
environment:
VAULT_ADDR: http://shared-vault:8200
VAULT_TOKEN: ${VAULT_TOKEN}
volumes:
- ./additional_config/vault-init.sh:/scripts/init.sh:ro

entrypoint: [
"sh", "-c",
"apk add --no-check-certificate --no-cache curl jq openssl \
&& tr -d '\r' < /scripts/init.sh > /tmp/init.sh \
&& sh /tmp/init.sh"
]
restart: "no"
networks:
- con-x-test-network

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

vault-init läuft bei jedem up und überschreibt die Key. Das Skript schreibt prov_priv/prov_pub und provider-wallet-aes-key-alias bedingungslos neu. Im Memory-Setup egal, im persistenten nicht: Die Postgres-Daten überleben im pgdata-Volume, die Keys rotieren aber bei jedem Neustart. Alles, was das Wallet mit dem alten AES-Key verschlüsselt abgelegt hat, ist danach nicht mehr entschlüsselbar. Das Skript sollte idempotent sein (vorher GET secret/data/ oder Schreiben mit cas=0)

provider-controlplane:
container_name: provider-controlplane
image: ghcr.io/project-construct-x/con-x-controlplane-postgresql-hashicorp-vault:latest
pull_policy: never

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ich verstehe nicht so ganz, warum habt ihr entschieden den pull_policy auf never zu definieren?

provider-dataplane:
container_name: provider-dataplane
image: ghcr.io/project-construct-x/con-x-dataplane-postgresql-hashicorp-vault:latest
pull_policy: never

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hier auch die gleiche Frage

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants