Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion guides/deployment/microservices.md
Original file line number Diff line number Diff line change
Expand Up @@ -138,7 +138,7 @@ These are the (not so beneficial) side effects you when using a shared persisten

> Note how *NPM workspaces* allows us to use the package names of the projects, and nicely creates symlinks in *node_modules* accordingly.

2. Add a `db/schema.cds` file as a mashup to actually collect the models:
2. Add a `shared-db/db/schema.cds` file as a mashup to actually collect the models:

::: code-group
```cds [shared-db/db/schema.cds]
Expand All @@ -154,6 +154,10 @@ These are the (not so beneficial) side effects you when using a shared persisten

With that we're basically done with the setup of the collector project. In sum, it's just another CAP project with some cds models in it, which we can handle as usual. We can test whether it all works as expected, for example, we can test-compile and test-deploy it to sqlite and hana, build it, and deploy it to the cloud as usual:

```sh
cd shared-db
```

```sh
cds db -2 sql
```
Expand All @@ -168,6 +172,10 @@ cds deploy -2 sqlite
cds build --for hana
```

```sh
cd ..
```

> Note: As we can see in the output for `cds deploy` and `cds build`, it also correctly collects and adds all initial data from enclosed `.csv` files.
:::

Expand Down