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, the startup summary included:
nexus: client readyatinfo, naming the configs, secrets and flags the first sync delivered - never a value. 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
Local development
westyx dev run php artisan serve needs no Nexus settings: NEXUS_BASE_URL falls back to WESTYX_SERVICE_ENDPOINT, which the CLI sets, and with no NEXUS_API_KEY and NEXUS_WIF_ENABLED unset the provider uses WIF, which reaches the session westyx dev setup stored. Set NEXUS_WIF_ENABLED=false to turn that default off.
Under PHP-FPM the variable is not visible to workers by default (clear_env = yes); see Configuration.
Framework settings stay in .env
APP_ENV, APP_KEY, DB_CONNECTION and the rest of Laravel’s own settings cannot come from Nexus: Laravel reads .env while it bootstraps, before any service provider registers, so a Nexus config of that name changes nothing. Keep them in the environment, and read what your own code decides at runtime from Nexus.
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.
