Skip to content

Commit 4246c38

Browse files
committed
docs: improve Readme
1 parent 58b5715 commit 4246c38

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -165,12 +165,12 @@
165165

166166
### Working on `taas-es-processor` locally
167167

168-
When you run `taas-apis` locally as per "[Steps to run locally](#steps-to-run-locally)" the `taas-es-processor` would be run for you automatically together with other services inside the docker container when you run `npm run services:up`.
168+
When you run `taas-apis` locally as per "[Steps to run locally](#steps-to-run-locally)" the [taas-es-processor](https://github.com/topcoder-platform/taas-es-processor) would be run for you automatically together with other services inside the docker container via `npm run services:up`.
169169

170170
To be able to change and test `taas-es-processor` locally you can follow the next steps:
171171

172172
1. Stop `taas-es-processor` inside docker by running `docker-compose -f local/docker-compose.yml stop taas-es-processor`
173-
2. Run `taas-es-processor` separately from the [source code](https://github.com/topcoder-platform/taas-es-processor). As `npm run services:up` already run all the dependencies for both `taas-apis` and for `taas-es-processor`. The only thing you need to do for running `taas-es-processor` locally is:
173+
2. Run `taas-es-processor` separately from the source code. As `npm run services:up` already run all the dependencies for both `taas-apis` and for `taas-es-processor`. The only thing you need to do for running `taas-es-processor` locally is clone the [taas-es-processor](https://github.com/topcoder-platform/taas-es-processor) repository and inside `taas-es-processor` folder run:
174174
- `nvm use` - to use correct Node version
175175
- `npm run install`
176176
- `npm run start`

0 commit comments

Comments
 (0)