Configuring the clients requires some knowledge of the services first. After understanding what each service does and how it fits into the pipeline, you will be more informed as to how you wish to scale and manage those services.
Please note that GRPC services do not use URLs. Just host:port combinations. All the internal services use GRPC.
clients: logsvc: 'localhost:6005' datasvc: 'localhost:6000' queuesvc: 'localhost:6001' assetsvc: 'localhost:6002'
For now accept that each service runs on the following ports. These will be configurable in the future.
- datasvc: 6000
- queuesvc: 6001
- assetsvc: 6002
- logsvc: 6005
- uisvc: 6010 -- but no internal services query the uisvc.
Clients may optionally configure TLS Authentication
for servers that require it. To do this, add a
tls key with some
sub-parameters inside the
clients section, like so:
clients: tls: ca: /var/ca/rootCA.pem cert: /var/ca/localhost-client.pem key: /var/ca/localhost-client.key datasvc: 'localhost:6000' queuesvc: 'localhost:6001' assetsvc: 'localhost:6002' logsvc: 'localhost:6005'
Please note if a client fails to connect it will typically not result in a server error -- you must diagnose this by reading the logs.