Skip to content

Tool Setup

Use this before Lesson 01. The course targets Linux first.

Required

Git

Install a current Git and verify:

bash
git --version

Official downloads/docs: https://git-scm.com/downloads

Go

The planned core baseline is Go 1.26.x. Use the latest compatible patch release available to you and record it when you bootstrap the repository.

Official install: https://go.dev/doc/install

bash
go version

Bun

Bun is the package manager and JavaScript tooling entrypoint for the whole repository. It manages the VitePress documentation site now and the Electron/React workspace later.

Official install: https://bun.sh/docs/installation

bash
bun --version

After cloning/unzipping the starter, install the root JavaScript dependencies and verify the documentation site:

bash
bun install
bun run docs:dev

Use bun run docs:build for a production documentation build. VitePress officially documents Bun as a supported install/run path: https://vitepress.dev/guide/getting-started

Node runtime compatibility

Electron bundles Chromium/Node for packaged runtime, while development tooling may have its own requirements. Follow the current Electron/Vite requirements when Lesson 01 pins dependencies; do not copy stale version numbers from old chats.

Added during Lesson 02

Buf / Protocol Buffers tooling

Buf install: https://buf.build/docs/cli/installation/

Connect docs: https://connectrpc.com/

Install these when the course reaches the generated RPC boundary rather than front-loading every tool today.

Useful optional tools

  • sqlite3 CLI for inspecting test/dev databases: https://sqlite.org/cli.html
  • jq for inspecting JSON/JSONL
  • watchexec or similar for local development loops (optional; do not make architecture depend on it)

Verify your environment

Record output in your own terminal/notes if something differs:

bash
git --version
go version
bun --version

If a course command differs on your distribution, update the current setup doc so future sessions/agents use the working command.

Forge is local-first. The docs are part of the product engineering system.