From 717554b5555a2d45fb4c1137127bd4ff02b496d1 Mon Sep 17 00:00:00 2001 From: DJ Adams Date: Tue, 16 Jun 2026 16:49:22 +0100 Subject: [PATCH] fix local binding registry filename in reuse-and-compose.md The file starts with a dot and this was omitted in a couple of places in this section. --- guides/integration/reuse-and-compose.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/guides/integration/reuse-and-compose.md b/guides/integration/reuse-and-compose.md index 5b9de77126..a0bbb14e1f 100644 --- a/guides/integration/reuse-and-compose.md +++ b/guides/integration/reuse-and-compose.md @@ -594,9 +594,9 @@ You can cmd/ctrl-click or double click on that to see the file's content, and fi Whenever you start a CAP server with `cds watch`, this is what happens automatically: -1. For all *provided* services, corresponding entries are written to _~/cds-services.json_ with respective `credentials`, namely the `url`. +1. For all *provided* services, corresponding entries are written to _~/.cds-services.json_ with respective `credentials`, namely the `url`. -2. For all *required* services, corresponding entries are fetched from _~/cds-services.json_. If found, the `credentials` are filled into the respective entry in `cds.env.requires.` [as introduced previously](#bindings-via-cds-env). +2. For all *required* services, corresponding entries are fetched from _~/.cds-services.json_. If found, the `credentials` are filled into the respective entry in `cds.env.requires.` [as introduced previously](#bindings-via-cds-env). In effect, all the services that you start locally in separate processes automatically receive their required bindings so they can talk to each other out of the box.