if you want to run a microservice in nx workspace with dapr, rename the serve target to e.g. x-serve target and use nx:run-commands executor to run dapr with the parameter yarn nx run yourproject-name:serve
Here is an example for project called timeline-microservice:
"x-serve": {
"executor": "@nrwl/js:node",
| { | |
| "name": "JoyItRobot", | |
| "description": "", | |
| "parentTypeId": "core.basicasset", | |
| "instantiable": true, | |
| "scope": "private", | |
| "aspects": [ | |
| { | |
| "name": "SensorData", | |
| "aspectTypeId": "castidev.RobotSensorData" |
| { | |
| "name": "RobotSensorData", | |
| "category": "dynamic", | |
| "scope": "private", | |
| "description": "The root schema comprises the entire JSON document.", | |
| "variables": [ | |
| { | |
| "name": "blocked", | |
| "dataType": "BOOLEAN", | |
| "unit": ".", |
| { | |
| "$schema": "http://json-schema.org/draft-07/schema", | |
| "$id": "http://example.com/example.json", | |
| "type": "object", | |
| "title": "The root schema", | |
| "description": "The root schema comprises the entire JSON document.", | |
| "default": {}, | |
| "examples": [ | |
| { | |
| "blocked": false, |
| { | |
| "$schema": "http://json-schema.org/draft-07/schema", | |
| "$id": "http://example.com/example.json", | |
| "type": "object", | |
| "title": "The root schema", | |
| "description": "The root schema comprises the entire JSON document.", | |
| "default": {}, | |
| "examples": [ | |
| { | |
| "servos": { |
| { | |
| "blocked": false, | |
| "vibration": true, | |
| "servo1_temp": 21.67 | |
| } |
| { | |
| "servos": { | |
| "servo0": 2366, | |
| "servo1": 2366, | |
| "servo2": 2100, | |
| "servo3": 1672, | |
| "servo4": 2086, | |
| "servo5": 1500, | |
| }, | |
| "angles": { |
If you are moving your development machine from an unrestricted to a restricted network and back, the chances are high that you will have problems using ssh or git dependent on the network where your computer is currently set up.
A good way to circumvent this is to use a local development proxy (like fiddler) on your computer and to tunnel all connections through it.
For example I am running fiddler on my machine on port 8888 (accepting external connections) and I am using the following setup: