Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs: update AppConfig file directories in README.md #183 #241

Merged
merged 1 commit into from
Apr 9, 2024
Merged

docs: update AppConfig file directories in README.md #183 #241

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
11 changes: 6 additions & 5 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,12 +33,13 @@ docker compose --profile ui -f system-tests/docker-compose.yml up --build

> In Windows Docker Compose expects the path to use forward slashes instead of backslashes.

The profile `ui` creates three Data Dashboards each connected to an EDC participant. The respective `app.config.json`
files can be found in the respective directories:
The profile `ui` creates three Data Dashboards each connected to an EDC participant.
Each of these Data Dashboards uses the respective `app.config.json` file which is stored in the
respective directories:

- `resources/appconfig/company1/app.config.json`
- `resources/appconfig/company2/app.config.json`
- `resources/appconfig/company3/app.config.json`
- [`./system-tests/resources/appconfig/company1/app.config.json`](./system-tests/resources/appconfig/company1/app.config.json)
- [`./system-tests/resources/appconfig/company2/app.config.json`](./system-tests/resources/appconfig/company2/app.config.json)
- [`./system-tests/resources/appconfig/company3/app.config.json`](./system-tests/resources/appconfig/company3/app.config.json)

That's it to run the local development environment. The following section `Run A Standard Scenario Locally` describes a
standard scenario which can be optionally used with the local development environment.
Expand Down
Loading