Install

Install ForgeOS from a source you can verify

Two ways in. Both end at the same place: your project carries the portable half of ForgeOS and passes its own validation suite. There is no curl-into-a-shell — ForgeOS's own safety hook refuses it.

Cited release v1.20.1

Supported paths

Use the checksummed release artifact when you want a pinned, reviewable source.

Use a clone when you want to inspect the repository first or start from a specific tag.

Use the platform installer only to prepare a local forgeos command; it does not adopt project files.

The release artifact and checksum are published together: archive · checksum · release notes.

Commands

From the release artifact — recommended

Download the archive and its checksum from the latest release, verify before you trust it, then sync into your project. The first sync is a dry run; review it, then apply. The same two steps upgrade a project that already adopted ForgeOS: files you customized are skipped, and your own records are never touched.

POSIX bash

sha256sum -c forgeos-1.20.1.tar.gz.sha256
tar -xzf forgeos-1.20.1.tar.gz
bash forgeos-1.20.1/scripts/blueprint/sync-blueprint.sh --source forgeos-1.20.1 --target <project>
bash forgeos-1.20.1/scripts/blueprint/sync-blueprint.sh --source forgeos-1.20.1 --target <project> --apply

Windows PowerShell

(Get-FileHash -Algorithm SHA256 forgeos-1.20.1.tar.gz).Hash
tar -xzf forgeos-1.20.1.tar.gz
powershell -NoProfile -ExecutionPolicy Bypass -File forgeos-1.20.1/scripts/blueprint/sync-blueprint.ps1 -Source forgeos-1.20.1 -Target <project>
powershell -NoProfile -ExecutionPolicy Bypass -File forgeos-1.20.1/scripts/blueprint/sync-blueprint.ps1 -Source forgeos-1.20.1 -Target <project> -Apply

From a clone

Start a new project from the repository itself — then make the history yours.

New project

git clone https://github.com/Anasabdellatif/forgeos.git my-project
cd my-project
rm -rf .git && git init -b main

Prepare a local forgeos command

The platform installers write a local command shim or launcher into a directory you choose. They fetch nothing, do not edit PATH, and verify a checksum when the source came from a release artifact.

POSIX installer

bash scripts/install/install-forgeos.sh --source <forgeos> --destination <tools-dir>
bash scripts/install/install-forgeos.sh --source <forgeos> --destination <tools-dir> --apply
<tools-dir>/forgeos doctor

Windows installer

powershell -NoProfile -ExecutionPolicy Bypass -File scripts/install/install-forgeos.ps1 -Source <forgeos> -Destination <tools-dir>
powershell -NoProfile -ExecutionPolicy Bypass -File scripts/install/install-forgeos.ps1 -Source <forgeos> -Destination <tools-dir> -Apply
<tools-dir>\forgeos.ps1 doctor

Then, in either case

The first run is expected to report unfilled markers: those are the facts your project must supply. The adoption step is the product — an unadopted blueprint gives structure with no knowledge.

Validate on POSIX

bash scripts/validation/check-all.sh

Validate on Windows

powershell -NoProfile -ExecutionPolicy Bypass -File scripts/validation/check-all.ps1

No package managers yet — deliberately. Each channel is deferred on the roadmap with its blocker named. A local forgeos command and per-platform installer scripts ship in the repository, both proven on the platforms they claim.

After you install

Adoption is not finished when the files land: the first validation run lists the project facts only you can supply. These pages cover what comes next.