Verify Your Install

Once Fresh Computer Setup and Environment & Secrets are done, use these checks to confirm your environment is actually working before you start development.

1. Confirm the devbox/direnv shell loaded

echo $DEVBOX_PROJECT_ROOT
echo $AZURE_USERNAME

Both should print a value. If empty, direnv allow may not have run, or Azure hooks failed — see Environment & Secrets.

2. Sync the Python workspace

The repo root pyproject.toml defines a UV workspace containing packages/utils, packages/vcl, packages/db, and the in-workspace project packages (e.g. mx-com-reporting). From the repo root:

uv sync --all-groups --all-extras

This should resolve without errors and create/update .venv.

3. Run a package’s test suite

pytest packages/utils

Adjust the path to any package or project you’re working on.

4. Confirm the vcl CLI is on PATH

vcl --help

vcl is the Visory Command Line tool for scaffolding new projects/apps (see Packages → vcl). If it isn’t found, re-run direnv reload or check scripts/workspace-setup/03-uv-tool.sh ran successfully.

5. Install Node dependencies where needed

Devbox provisions Node/pnpm binaries but does not install each subproject’s node_modules. Run pnpm install inside each Node-based subproject you’ll work on:

cd docs && pnpm install        # this documentation site
cd web/site && pnpm install    # Visory's business site
cd apps/mx_fuels_reporting_app/apps/web && pnpm install   # dashboard

6. Confirm Astronomer CLI (only if touching orchestration)

astro version

Provisioned by scripts/workspace-setup/07-astronomer.sh. See Orchestration before running astro dev start.

If something fails

• Environment/secrets issues → Environment & Secrets
• Deeper architectural questions → the relevant persona in AI Experts, e.g. 01-monorepo-workspace-architect.md for workspace/tooling issues or 03-environment-security-engineer.md for auth/secrets issues