Setup
What comes from your container
Two things, so the SDK fits the application rather than the other way round:- The PSR-18 client. Nexus traffic goes through the HTTP stack your application already configures - its proxy settings, middleware and instrumentation apply. If nothing is bound, the SDK discovers whatever implementation the project has. See HTTP client.
- The PSR-3 logger. SDK diagnostics land in your application log with nothing to configure. See Custom logging.
Lazy by design
The binding is deferred and lazy. Creating a client performs a network round-trip, so nothing happens until something actually resolves
NexusClient - registering the provider costs nothing, and an application that never reads a config never pays for one.Configuration
The defaults apply whether or not you publish the file. Publish it to change anything beyond the environment variables:A dedicated log channel
Workload Identity Federation
On EKS, GKE, AKS or any Kubernetes cluster, drop the API key entirely:Live updates in a worker
connectStream() blocks and does not return, so it belongs in a dedicated console command rather than in a request:
queue:work. See SSE live updates.
