You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3-2Lines changed: 3 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -215,6 +215,7 @@ To be able to change and test `taas-es-processor` locally you can follow the nex
215
215
|`npm run services:up`| Start services via docker-compose forlocal development. |
216
216
|`npm run services:down`| Stop services via docker-compose forlocal development. |
217
217
|`npm run services:logs -- -f <service_name>`| View logs of some service inside docker-compose. |
218
+
|`npm run services:rebuild -- -f <service_name>`| Rebuild service container ignoring cache (useful when pushed something to the Git repository of service) |
218
219
|`npm run local:init`| Recreate Database and Elasticsearch indexes and populate demo data forlocal development (removes any existent data). |
219
220
|`npm run local:reset`| Recreate Database and Elasticsearch indexes (removes any existent data). |
220
221
|`npm run cov`| Code Coverage Report. |
@@ -337,6 +338,6 @@ When we add, update or delete models and/or endpoints we have to make sure that
337
338
- Test, that when we migrate DB from the previous state using `npm run migrate`, we get exactly the same DB schema as if we create DB from scratch using command `npm run init-db force`.
338
339
339
340
## EMSI mapping
340
-
mapping EMSI tags to topcoder skills
341
-
Run `npm run emsi-mapping` to create the mapping file
341
+
mapping EMSI tags to topcoder skills
342
+
Run `npm run emsi-mapping` to create the mapping file
342
343
It will take about 15 minutes to create the mapping file `script/emsi-mapping/emsi-skils-mapping.js`
0 commit comments