Skip to main content

Installation (Windows)

For Windows 10 / 11. The CLI runs natively on Windows; you do not need WSL2.

The flow is:

  1. Run the CLI in PowerShell to scaffold a project.
  2. Open the scaffolded project in VS Code.
  3. Reopen in Container — the Dev Container itself runs Linux, transparently, via Docker Desktop.
Spaces in your Windows user name

If your Windows account name contains a space (e.g. C:\Users\John Smith\...), %USERPROFILE% will also contain a space. This can still cause subtle failures in various Node / Python / gcloud tooling that doesn't quote paths properly. The Dev Container itself no longer bind-mounts files from %USERPROFILE%, so credential propagation is not affected — but if you hit unexplained path errors during this guide, a spaced user name is a likely culprit.

Prerequisites (one-time)​

  • Windows 10 22H2 or Windows 11.
  • Node.js LTS. Install from nodejs.org or via winget install OpenJS.NodeJS.LTS. Verify in PowerShell: 
    node -v
    npm -v
  • Docker Desktop. Install from docker.com. Start it once and let it finish initializing. On first launch, Docker Desktop will prompt for permission (UAC / file sharing / WSL integration) — you must grant it, otherwise the RevOS container setup will not be able to continue. Verify in PowerShell: 
    docker ps
  • VS Code. Install from code.visualstudio.com or via winget install Microsoft.VisualStudioCode. Then install the Dev Containers extension (publisher ms-vscode-remote) from the Marketplace, or run: 
    code --install-extension ms-vscode-remote.remote-containers

Install the CLI​

In PowerShell:

npm install -g @revos/cli
revos --version

First-time auth​

revos auth login

A browser window opens to complete the OAuth flow. Credentials are written to %USERPROFILE%\.revos\credentials.json.

Scaffold a project​

revos init my-project
cd my-project
code .

revos init writes the GCP service-account key to %USERPROFILE%\.revos\<project>-gsa-creds.json on the host. The Dev Container does not bind-mount this file — it persists credentials inside a per-project Docker named volume. You'll re-provision the key from inside the container in the next step.

In VS Code, click Reopen in Container when prompted (or run "Dev Containers: Reopen in Container" from the command palette).

Finish setup inside the container​

When the container is up, open a terminal inside it and run:

revos init          # signs you in via browser (if needed), then provisions the GCP key into ~/.revos

After this, the per-project named volume holds both your CLI login and the GCP service-account key. Future Rebuild Container invocations don't require re-running these — postStartCommand re-activates the service account on every start.

Verify​

  • docker ps from PowerShell succeeds.
  • revos auth status from PowerShell shows you logged in (host-side login, optional).
  • After Reopen in Container, VS Code's bottom-left badge shows Dev Container: ….
  • Inside the container terminal, after revos init: 
    revos auth status
    gcloud auth list
    Both should report active credentials.
  • Quickest sanity check. Open a new terminal inside the container and run: 
    dbt --version
    bq ls
    If both commands complete without errors, the setup is good — you're done.

Troubleshooting​

  • VS Code is stuck / something hangs and won't move forward — press Ctrl+Shift+P and run Developer: Reload Window. This usually unblocks frozen Dev Container or extension states.
  • docker ps fails — Docker Desktop is not running. Start it from the Start menu and wait for the whale icon to stop animating.
  • bq or dbt fails with "credentials not found" inside the container — you haven't completed in-container setup. Run revos init in the container terminal (it will prompt for sign-in if needed), then either rebuild the container or run bash .devcontainer/post-start.sh once to activate the service account.