Skip to content

Commit

Permalink
Added more instructions
Browse files Browse the repository at this point in the history
  • Loading branch information
basiliskus committed Jan 15, 2025
1 parent 45229d4 commit c676df1
Showing 1 changed file with 16 additions and 3 deletions.
19 changes: 16 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -444,10 +444,23 @@ with this option enabled.

1. Checkout `main` branch for `CDCgov/prime-reportstream`
2. Build RS (for more information please refer to the [ReportStream docs](https://github.com/CDCgov/prime-reportstream/blob/master/prime-router/docs/getting-started/README.md)):
- If building for the first time, run: `./cleanslate` in `prime-reportstream/prime-router`
- Otherwise run: `./gradlew clean package` in `prime-reportstream` root folder
- If building for the first time, run: `./cleanslate.sh` in `prime-reportstream/prime-router`
- **Note**: if you're using an Apple Silicon computer, before running the script edit `cleanslate.sh` to commentout the following lines:

```
if [ "$(uname -m)" = "arm64" ] && [[ $(uname -av) == _"Darwin"_ ]]; then
PROFILE=apple_silicon
SERVICES=(sftp azurite vault) # Only these services are M1 compatible
BUILD_SERVICES=(postgresql)
fi
```
- Otherwise, run: `./gradlew clean quickPackage` in `prime-reportstream` root folder
- **Note**: if attempting to access the metadata endpoint in RS add the variable `ETOR_TI_baseurl="http://host.docker.internal:8080"` to `prime-router/.vault/env/.env.local` file before building the container
3. Run RS with `docker compose up -d`. You may also use `./gradlew quickRun`
3. Run RS by starting the required docker containers:
- `docker compose up -d`
- `docker compose -f docker-compose.build.yml up -d`
- `docker compose -f docker-compose.postgres.yml up -d`
4. Run the RS setup script in this repository: `/scripts/setup/setup-reportstream.sh`
- Before running the script, make sure to follow the instructions in [/scripts/README.md](/scripts/README.md)
- You can verify the script created vault secrets successfully by going to `http://localhost:8200/` in your browser, use the token in `prime-router/.vault/env/.env.local` to authenticate, and then go to `Secrets engines` > `secret/` to check the available secrets
Expand Down

0 comments on commit c676df1

Please sign in to comment.