Open kkimdev opened 9 months ago
We are refactoring and improving the functions and documentation of mediator, please pay attention to our follow-up updates.
But maybe before refactoring I can also provide this functionality
Sounds great (either ways, before/after refactoring) ! Thanks for doing this project, (although we couldn't use Mediator due to this issue) it looks great and almost just what we need!
I have some question for it.
Thanks for asking!
1. User web browser
-> 2. Our Kubernetes ingress
(SSL is terminated here.) -> 3. Envoy grpc-web proxy
(that converts unencrypted grpc-web to unencrypted grpc) -> 4. NodeJS grpc server
And we would like to put a gRPC proxy debugger between step 3 and 4 on the development path for debugging.
make watch-dev
script. So we need to launch Mediator from a script with all the configurations. In the case of Proxide, it was as simple as proxide monitor -l 5555 -t http://localhost:8081
and it worked well.install[...].sh
. For example, proxide
could be installed just with cargo install proxide
so it was pretty convenient. Even better, Nix package would be awesome since then that's just one line change in our flake.nix
config, though it's not the end of the world without that.Proxide checked most of the boxes, though critically, it didn't support proto Server reflection and the latest proto 3 spec, so we couldn't use that. And Mediator
UI looks a lot nicer :)
Similar to https://github.com/Rantanen/proxide#direct-connection-to-proxide , it would be convenient to have a direct connection mode, so that Mediator can be used even when we don't have a great control over client configurations / cumbersome to change them.