DEVELOPMENT / CLI DISTRIBUTION

Install Dowe

Install the versioned Dowe CLI from the official release channel, then use the same binary for development, testing, builds, and deployment.

Open Dowe Dev

OFFICIAL INSTALLERS

Install from get.dowe.dev

The platform installer downloads the matching archive from the latest channel and places the binary in the user install directory.

dowe
curl -fsSL https://get.dowe.dev/install | bash
irm https://get.dowe.dev/install.ps1 | iex

MACOS + LINUX

One shell installer

The Bash installer selects the matching macOS or Linux archive and updates the user PATH when the install directory is not already present.

WINDOWS

PowerShell native flow

The PowerShell installer downloads the Windows archive, places the binary and Dowe font catalog under the user directory, and updates the user PATH when needed.

USER-OWNED INSTALLATION

Choose the version and location

Use installer environment variables when a project, workstation image, or CI runner needs a different release channel or destination.

dowe
DOWE_VERSION=1.2.3 curl -fsSL https://get.dowe.dev/install | bash
DOWE_INSTALL_DIR=/opt/dowe/bin curl -fsSL https://get.dowe.dev/install | bash
DOWE_BASE_URL=https://releases.example.test curl -fsSL https://releases.example.test/install | bash

DOWE_VERSION

Pin a release

Use latest by default or provide a version such as 1.2.3.

DOWE_INSTALL_DIR

Choose a directory

macOS and Linux default to $HOME/.dowe/bin; Windows defaults to the user .dowe/bin directory.

DOWE_BASE_URL

Use another channel

Point the installer at a compatible release CDN or private mirror.

WINDOWS TROUBLESHOOTING

Expose the installer error

Empty installer variables are treated as unset. If PowerShell reports a null method error, download the script first to expose whether the response or the installer failed.

dowe
$installer = irm https://get.dowe.dev/install.ps1
if ([string]::IsNullOrWhiteSpace($installer)) { throw "The installer response is empty" }
iex $installer

VERIFY AND UPGRADE

Keep the CLI current

After installation, verify the binary and let Dowe delegate future upgrades to the same platform installer instead of duplicating installation logic.

dowe
dowe version
dowe upgrade

VERSION

Confirm the binary

dowe version prints the installed CLI version so scripts and support reports can identify the toolchain.

UPGRADE CHECK

Compare latest metadata

dowe upgrade checks latest/version and only installs when the published version is newer.

FAILURE SAFETY

Stop on invalid releases

Invalid metadata and unsupported platforms produce a clear error instead of a partial upgrade.

REMOVE THE CLI

Uninstall without touching projects

Dowe removes the installed binary, its packaged font catalog, the managed PATH entry, and only empty installation directories. Project source, project .dowe data, and unrelated files remain untouched.

dowe
dowe uninstall
dowe uninstall --yes

CONFIRMATION

Review before removal

dowe uninstall asks for confirmation in a terminal. Use --yes when a script already owns the decision.

THREE PLATFORMS

macOS, Linux, and Windows

Unix removes the executable before exit. Windows schedules removal after the current process closes.

SAFE BOUNDARY

Keep application data

Dowe does not delete project files, project .dowe directories, application data, credentials, or unrelated install-directory files.

READY TO BUILD

Move from installation to a project

Once the CLI is available, initialize a project or enter an existing Dowe root and start the shared development workflow.

New project

Use dowe init --template blank, or choose CRUD from the interactive menu and continue to the optional i18n step. A root main.dowe marks an existing project.

Existing project

Run dowe dev --target server --target web to start it. If you invoke interactive dowe init here, Dowe asks before replacing managed template files and defaults to keeping the project unchanged.

Read Deploy docs