Skip to content

SETUP.md

Latest commit

 

History

History
81 lines (57 loc) · 2.74 KB

SETUP.md

File metadata and controls

81 lines (57 loc) · 2.74 KB

Setup new tools

Recommend to use [iterm2] as Mac terminal.

Libraries needed to install when setting up on a new computer:

After installing brew simply run:

brew install direnv
brew install selecta
brew install diff-so-fancy
brew install ripgrep
brew install shellcheck
brew install nvm
brew install pyenv
brew install chruby
brew install ruby-install

ruby-install # see version
pyenv install # see version

Terminal tools:

  • brew: package manager for macOS (or Linux)
  • direnv: unclutter your .profile
  • selecta: a fuzzy text selector for files and anything else you need to select
  • diff-so-fancy: good-lookin' diffs
  • ripgrep: recursively searches directories for a regex pattern while respecting your gitignore
  • shellcheck: static analysis for shell scripts
  • semgrep: lightweight static analysis for many languages

Web development

  • nvm: Node Version Manager
  • pyenv: Python Version Manager
  • chruby: Ruby Version Manager
  • biome: Biome is a fast formatter for JavaScript, TypeScript, JSX, TSX

Cloud severless development

Pi setup

  • Install the Pi coding agent:

    npm install -g @mariozechner/pi-coding-agent

  • After running clone_and_link.sh once, store the OpenAI API key in macOS Keychain and configure Pi auth:

    bash scripts/setup-pi-openai-key.sh set

    The script only manages the openai entry in ~/.pi/agent/auth.json and preserves any other provider entries already stored there.

    Remove the stored Pi OpenAI key and auth entry:

    bash scripts/setup-pi-openai-key.sh unset

  • Global Pi settings are managed in files/.pi/agent/settings.json and linked to ~/.pi/agent/settings.json by clone_and_link.sh without replacing the rest of ~/.pi or overwriting ~/.pi/agent/auth.json.

  • If a previous broken clone_and_link.sh run removed ~/.pi/agent/auth.json, recreate it with:

    bash scripts/setup-pi-openai-key.sh set

    If the script reports a legacy ~/.pi symlink, run bash clone_and_link.sh first so it can repair ~/.pi before writing Pi auth.