Skip to main content

​
Prerequisites

​
1. Log in

A browser window opens for authentication. On headless machines (SSH, Docker, CI), the device flow is used automatically - the CLI prints a short URL and code to enter in your browser.
To force device flow on a machine with a browser:
After login, the CLI auto-selects your first tenant and project. Check what was picked:

​
2. Set your active tenant and project

The active context is saved to ~/.config/westyx/config.json and used as the default for all subsequent commands. You can override it for a single command with --tenant / --project.

​
3. New project - migrate from .env

If you have an existing .env file, westyx analyze classifies each entry and writes a .wx file ready to push:
Review the generated .westyx/.wx file, then push it to your personal Nexus dev environment:

​
3. Existing project - pull from Nexus

If the project is already in Nexus, pull the current state:
This creates .westyx/.wx with all services, secrets, configs, and flags.

​
4. Start your app with Nexus values

With scripts defined in .westyx/config:
Without scripts, override the command directly:
Nexus values are injected as environment variables. If Nexus is unreachable, cached values from .westyx/.wx are used automatically.

​
Developer WIF (optional)

For a tighter local setup, configure Developer WIF so the Nexus SDK in your app detects credentials automatically - no api_key in your local config:
After setup, start your app normally. The SDK picks up the credentials from ~/.config/westyx/dev-credentials.yaml. Check credential status:
Remove when done:

​
New machine workflow

For a developer joining a project that already uses Westyx:

​
Next steps

Command reference

Full reference for every command and flag.

CI/CD

Use the CLI in automated pipelines.