Recently we have decided to give dapr a try with our microservices.
Yesterday when I started to test with docker the following config was strange to me,
the -app-port config on the sidecards looks wrong. Shouldn't it be listening to what the actual app is listening too (It is the same as the cli right? https://docs.dapr.io/reference/cli/dapr-run/)?
I am setting it up with redis pubsub and two dotnet core webapis and with following this config I couldn't get it to work so I change the -app-port from 3000 to the port my app was really listening too and it worked.
But I think maybe its because in your case it is gRPC? I'm not sure.
But thanks for the documentation anyway at least it is there in most cases its not for other libraries/packages. 😊
Hi,
Recently we have decided to give dapr a try with our microservices. Yesterday when I started to test with docker the following config was strange to me, the
-app-port
config on the sidecards looks wrong. Shouldn't it be listening to what the actual app is listening too (It is the same as the cli right? https://docs.dapr.io/reference/cli/dapr-run/)?I am setting it up with redis pubsub and two dotnet core webapis and with following this config I couldn't get it to work so I change the -app-port from
3000
to the port my app was really listening too and it worked. But I think maybe its because in your case it is gRPC? I'm not sure.But thanks for the documentation anyway at least it is there in most cases its not for other libraries/packages. 😊