Resync farrow.pgsty.com with the one-deployment simplification and give the roadmap a home
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1
- Forks
- 0
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 1
Description
Why
The site was resynced for the morning redesign on 2026-08-27, before the same-day simplification removed projects, leases, forwards:, list/repair/debug-bundle, exit code 6, and the version:/nodes: config form. Pages that still describe those are wrong. The Terraform-provider direction (a thin terraform-provider-farrow over the engine, its trigger conditions, and the engine disciplines that hold regardless) has had no page since phase-2.md was removed from this repository.
Proposed shape
- Audit every page against
farrow --help, the 0.1.0CHANGELOG.md, and theCONTRIBUTING.mdnon-negotiables; regenerate the CLI reference from the Cobra tree rather than by hand. - Add a roadmap page carrying the provider paragraph and the deferred items.
- Re-verify the native-replay evidence on the status page against a current build and cite that build.
Acceptance
- No page mentions projects, leases,
farrow list,farrow repair,debug-bundle,forwards:, or exit code 6. - The status page names the version it was verified with.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the documentation pages with farrow --help, the 0.1.0 CHANGELOG.md, and CONTRIBUTING.md; the removed phase-2.md identifies the missing roadmap context. Recheck the status page's native-replay evidence against a current build. Done means the listed obsolete terms are absent, the CLI reference reflects the Cobra tree, and the status page cites its verification version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, terraform
- Domain
- cli, devops, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100