Skip to content
PolyForge

Setting up a new machine

This is the scenario PolyForge is built for. Start to finish, it is five commands.

  1. Clone.

    Terminal window
    git clone git@github.com:rizaldevv/polyforge.git
    cd polyforge

  2. Activate. Installs mise if needed, runs the trust handshake, registers all three commands.

    Terminal window
    .\polyforge.ps1 activate

    Then open a new shell.

  3. Look before you leap.

    Terminal window
    polyforge status

  4. Install the toolchain.

    Terminal window
    polyforge install

    This is the long step. Everything before it was near-instant.

  5. Warp your content back.

    Terminal window
    polyforge get all    # portfolio projects → Workspace/<lang>/
    learn get all        # learning tracks    → Dev/Learn/
    forge get all        # templates          → Dev/Templates/

You are where you left off.

What you need on the new machine

Section titled “What you need on the new machine”
For Requirement
Steps 1–5 git, and SSH access to your repositories
Publishing later gh (GitHub CLI), logged in

Note that restoring needs no GitHub CLI. You can be fully productive before you have authenticated gh — that only matters when you next publish something.

Verifying

Section titled “Verifying”
Terminal window
polyforge doctor
learn list go
forge list

doctor covers the environment; learn list and forge list confirm your content came back.

If something is missing

Section titled “If something is missing”

A project that exists on GitHub but did not restore is almost always missing from the registry — check that the machine you published from actually committed and pushed polyforge.registry.toml. See content separation and troubleshooting.