Skip to content
Pogo

Installation

Pogo can be installed through various package managers or built from source. Choose the method that works best for your platform.

Package Managers

Section titled “Package Managers”

NPM

Section titled “NPM”

The easiest cross-platform installation method, but the Node.js wrapper might make it slightly slower. Not recommended for older machines.

Terminal window
npm install -g @pogo-vcs/pogo

Homebrew (macOS and Linux)

Section titled “Homebrew (macOS and Linux)”
Terminal window
brew install --cask pogo-vcs/tap/pogo

Scoop (Windows)

Section titled “Scoop (Windows)”
Terminal window
scoop bucket add pogo-vcs https://github.com/pogo-vcs/scoop-bucket.git
scoop install pogo

Building from Source

Section titled “Building from Source”

If you prefer to build Pogo from source or need the latest development version:

Prerequisites

Section titled “Prerequisites”

Before building, ensure you have:

Build Steps

Section titled “Build Steps”
  1. Clone the repository:
    Terminal window
    git clone https://github.com/pogo-vcs/pogo.git
    cd pogo
  2. Build the binary:
    Terminal window
    just build
  3. The pogo binary will be created in the current directory. Move it to your PATH.

Shell Completion

Section titled “Shell Completion”

Pogo supports shell completion for better command-line experience.

Bash

Section titled “Bash”
Terminal window
# Load completion for current session
source <(pogo completion bash)


# Linux - permanent installation
pogo completion bash > /etc/bash_completion.d/pogo


# macOS - permanent installation
pogo completion bash > $(brew --prefix)/etc/bash_completion.d/pogo

Zsh

Section titled “Zsh”
Terminal window
# Load completion for current session
source <(pogo completion zsh)


# Permanent installation
pogo completion zsh > "${fpath[1]}/_pogo"

Fish

Section titled “Fish”
Terminal window
# Load completion for current session
pogo completion fish | source


# Permanent installation
pogo completion fish > ~/.config/fish/completions/pogo.fish

PowerShell

Section titled “PowerShell”
Terminal window
# Load completion for current session
pogo completion powershell | Out-String | Invoke-Expression


# Add to your PowerShell profile for permanent installation

Verification

Section titled “Verification”

After installation, verify that Pogo is working correctly:

Terminal window
# Check version
pogo --version


# View help
pogo --help


# Test server connectivity (if you have access to a server)
pogo init --name test-repo --server your-server:8080

Updating

Section titled “Updating”

NPM

Section titled “NPM”
Terminal window
npm update -g @pogo-vcs/pogo

Homebrew

Section titled “Homebrew”
Terminal window
brew upgrade pogo

Scoop

Section titled “Scoop”
Terminal window
scoop update pogo

From Source

Section titled “From Source”
Terminal window
cd pogo
git pull
just build
# update the binary in your PATH

Uninstallation

Section titled “Uninstallation”

NPM

Section titled “NPM”
Terminal window
npm uninstall -g @pogo-vcs/pogo

Homebrew

Section titled “Homebrew”
Terminal window
brew uninstall pogo

Scoop

Section titled “Scoop”
Terminal window
scoop uninstall pogo

Troubleshooting

Section titled “Troubleshooting”

Command Not Found

Section titled “Command Not Found”

If pogo is not found after installation:

  1. Restart your terminal or reload your shell configuration

  2. Check if it’s in your PATH:

    Terminal window
    which pogo  # Linux/macOS
    where pogo  # Windows

  3. For NPM installations, ensure global npm bin is in PATH:

    Terminal window
    npm bin -g

Permission Errors

Section titled “Permission Errors”

If you encounter permission errors during NPM installation:

Terminal window
# Use a Node version manager instead of sudo
# Or configure npm to use a different directory
npm config set prefix ~/.npm-global
export PATH=~/.npm-global/bin:$PATH

Build Errors

Section titled “Build Errors”

When building from source:

  1. Ensure all prerequisites are installed
  2. Check Go version: go version (needs 1.25+)
  3. Run go mod tidy to install Go dependencies
  4. Check the GitHub issues for known problems

Next Steps

Section titled “Next Steps”