Marco Argentieri
Marco Argentieri
> a new binary target here Do you mean to specify multiple binaries, so it would be compiled to two different executables one with the JSONRPC and one with gRPC...
I'm serving on the same interface (host:port) both gprc and grpc-web with TLS termination. Meaning that I already have a multiplexer that handle this in my go code, namely I...
@jonnywei Do you mean to add in my client request header? I'm afraid this could be a no-go if I need to ask client s (which are not run by...
> @tiero Running into the exact same issue, any luck figuring it out? No unfortunately. I ended up implementing TLS via certmagic in gocode directly But would be nice to...
Hey @jbrown-stripe we refactored the server multiplexer and we used your same Caddy configuration, still we cannot route gRPC via caddy as reverse proxy, just grpc-web actually. Ref: https://github.com/tdex-network/tdex-daemon/pull/423 Can...
@kostyay same thing. I suspect main problem is that we should be able to have a new directive that can switch transport based on content-type (the trick we do in...
This issue can be closed? Also is there a way to see the CPU, Memory etc.. of the remote host inside the coolify control pane?
I think this is a superset of this issue https://github.com/coollabsio/coolify/issues/300
> automatic backup of the entire setup would be great, with an option to restore +1 It can be a proprietary format ie. that backups volumes, databases & configuration, to...
> you could just use make client on Mac In the Makefile you linked there is no `client` target AFAICT