Prerequisites
westyxinstalled - see Installation- A Nexus account - request access at app.westyx.dev
1. Log in
2. Set up the project
In the project’s directory:- Workspace. With no
.westyx/config, it writes one from your active tenant, project and environment. To pick different ones first:westyx tenant set <name>,westyx project set <name>,westyx environment set <name>. - Values. With no
.westyx/.wx, it pulls the project’s values from Nexus. For a project not yet in Nexus it analyzes your.envinto.westyx/.wx- review it, then upload it withwestyx dev push- and offers to remove the
WESTYX_*connection settings you no longer need.
- and offers to remove the
- Credentials. It issues a Developer WIF session for every service your scripts name, so your application authenticates as you, with no API key on the machine.
.westyx/config, one script per process:
westyx dev setup --env-file, which writes .env.westyx and adds it to .gitignore.
3. Start your app
WESTYX_SERVICE_ENDPOINT, which the Nexus SDK reads - so the Nexus client in your code needs neither
an endpoint nor a key. If Nexus is unreachable, cached values from .westyx/.wx are used. When a
session expires, dev run says so and names the command that renews it.
New machine workflow
For a developer joining a project that already uses Westyx:westyx logout then westyx login: logout removes everything of the previous
account from the machine.
Next steps
Command reference
Full reference for every command and flag.
CI/CD
Use the CLI in automated pipelines.
