Skip to content

Install And Verify

Goal

Choose one installation channel, verify the active runtime immediately, and avoid carrying ambiguous installs into later automation.

flowchart LR
    A[Choose one channel] --> B[Install bijux-cli]
    B --> C[Run verification commands]
    C --> D{Status acceptable?}
    D -->|Yes| E[Continue to command usage]
    D -->|No| F[Resolve path or install conflicts]

This flowchart shows the recommended install posture: commit to one channel, verify immediately, and treat warning or degraded results as recovery work to solve before you move on to normal command use.

sequenceDiagram
    participant U as User
    participant S as Shell
    participant B as bijux
    U->>S: install bijux-cli
    U->>B: bijux version
    B-->>U: runtime identity
    U->>B: bijux cli paths
    B-->>U: active binary and state paths
    U->>B: bijux doctor
    B-->>U: install health report

The sequence diagram turns that advice into the exact first-run check. Each command answers a different question about runtime identity, active paths, and install health, so skipping one leaves a real blind spot.

  • cargo install --locked bijux-cli
  • python -m pip install --upgrade bijux-cli
  • pipx install bijux-cli

Pick one. Using several channels at once is possible, but it increases the chance of path ambiguity and stale wrappers.

Verify Immediately

Run:

bijux version
bijux cli paths
bijux doctor

These commands answer three different questions:

  • does bijux resolve at all
  • which binary and state paths are active
  • whether the current install reports ok, warning, or degraded, and whether another channel is shadowing it

Honest Rule

Do not treat an install as complete until bijux doctor is clean enough for your intended use. A command existing in PATH is not the same as a sound runtime setup.

Continue to Installation And Recovery.