I added a flag wsserver to the call-api-client since it was pulling from the config, but that config is for the call-api server and won't always match what the call-api-client wants to reach.
For example, my call-api-client command looked like this:
Not 100% sure if this will be useful to others. But, it help with my local docker development.
I could also see it being useful in production. If you want to test with the client against your call-api server, and you don't want to have a config locally that you keep up to date with production. With this you can quickly pass in the wsserver value.
I added a flag
wsserver
to the call-api-client since it was pulling from the config, but that config is for the call-api server and won't always match what the call-api-client wants to reach.For example, my call-api-client command looked like this:
Not 100% sure if this will be useful to others. But, it help with my local docker development.
I could also see it being useful in production. If you want to test with the client against your call-api server, and you don't want to have a config locally that you keep up to date with production. With this you can quickly pass in the
wsserver
value.