added NPM command to rebuild service in docker

Author: maxceem

README.md

@@ -215,6 +215,7 @@ To be able to change and test `taas-es-processor` locally you can follow the nex
 | `npm run services:up`                                                                                                     | Start services via docker-compose for local development.                                                                                           |
 | `npm run services:down`                                                                                                   | Stop services via docker-compose for local development.                                                                                            |
 | `npm run services:logs -- -f <service_name>`                                                                              | View logs of some service inside docker-compose.                                                                                                   |
+| `npm run services:rebuild -- -f <service_name>`                                                                           | Rebuild service container ignoring cache (useful when pushed something to the Git repository of service)                                           |
 | `npm run local:init`                                                                                                      | Recreate Database and Elasticsearch indexes and populate demo data for local development (removes any existent data).                              |
 | `npm run local:reset`                                                                                                     | Recreate Database and Elasticsearch indexes (removes any existent data).                                                                           |
 | `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
   - 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`.
 
 ## EMSI mapping
-mapping EMSI tags to topcoder skills    
-Run `npm run emsi-mapping` to create the mapping file    
+mapping EMSI tags to topcoder skills
+Run `npm run emsi-mapping` to create the mapping file
 It will take about 15 minutes to create the mapping file `script/emsi-mapping/emsi-skils-mapping.js`

package.json

@@ -25,6 +25,7 @@
     "services:up": "docker-compose -f ./local/docker-compose.yml --env-file .env up -d",
     "services:down": "docker-compose -f ./local/docker-compose.yml down",
     "services:logs": "docker-compose -f ./local/docker-compose.yml logs",
+    "services:rebuild": "docker-compose -f ./local/docker-compose.yml build --no-cache",
     "local:init": "npm run local:reset && npm run data:import -- --force",
     "local:reset": "npm run delete-index -- --force || true && npm run create-index -- --force && npm run init-db force",
     "cov": "nyc --reporter=html --reporter=text npm run test",