Snider f831fd6846 docs: restructure with Build/Publish sections and dynamic nav

- Move PHP and Go framework docs from /packages/ to /build/
- Move CLI docs from /packages/go/cmd/ to /build/cli/
- Add /publish/ section with docs for all release publishers:
  GitHub, Docker, npm, Homebrew, Scoop, AUR, Chocolatey, LinuxKit
- Add sidebar navigation for /publish/ section
- Update nav with Build, Publish, Deploy dropdowns
- Remove changelog, contributing, guide, and security sections
- Make sidebar auto-discover from packages, build, publish, deploy dirs

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

2026-01-29 22:20:32 +00:00

5.1 KiB

Raw Permalink Blame History

Migration Guide

Migrating from legacy scripts and tools to Core CLI.

From push-all.sh

The push-all.sh script has been replaced by core dev commands.

Legacy	Core CLI	Notes
`./push-all.sh --status`	`core dev work --status`	Status table
`./push-all.sh --commit`	`core dev commit`	Commit dirty repos
`./push-all.sh`	`core dev work`	Full workflow

Quick Migration

# Instead of
./push-all.sh --status

# Use
core dev work --status

New Features

Core CLI adds features not available in the legacy script:

# Quick health summary
core dev health
# Output: "18 repos │ clean │ synced"

# Pull repos that are behind
core dev pull

# GitHub integration
core dev issues      # List open issues
core dev reviews     # List PRs needing review
core dev ci          # Check CI status

# Dependency analysis
core dev impact core-php  # What depends on core-php?

From Raw Go Commands

Core wraps Go commands with enhanced defaults and output.

Raw Command	Core CLI	Benefits
`go test ./...`	`core go test`	Filters warnings, sets CGO_ENABLED=0
`go test -coverprofile=...`	`core go cov`	HTML reports, thresholds
`gofmt -w .`	`core go fmt --fix`	Uses goimports if available
`golangci-lint run`	`core go lint`	Consistent interface
`go build`	`core build`	Cross-compile, sign, archive

Why Use Core?

# Raw go test shows linker warnings on macOS
go test ./...
# ld: warning: -no_pie is deprecated...

# Core filters noise
core go test
# PASS (clean output)

Environment Setup

Core automatically sets:

CGO_ENABLED=0 - Static binaries
MACOSX_DEPLOYMENT_TARGET=26.0 - Suppress macOS warnings
Colour output for coverage reports

From Raw PHP Commands

Core orchestrates Laravel development services.

Raw Command	Core CLI	Benefits
`php artisan serve`	`core php dev`	Adds Vite, Horizon, Reverb, Redis
`./vendor/bin/pest`	`core php test`	Auto-detects test runner
`./vendor/bin/pint`	`core php fmt --fix`	Consistent interface
Manual Coolify deploy	`core php deploy`	Tracked, scriptable

Development Server Comparison

# Raw: Start each service manually
php artisan serve &
npm run dev &
php artisan horizon &
php artisan reverb:start &

# Core: One command
core php dev
# Starts all services, shows unified logs

From goreleaser

Core's release system is simpler than goreleaser for host-uk projects.

goreleaser	Core CLI
`.goreleaser.yaml`	`.core/release.yaml`
`goreleaser release --snapshot`	`core ci` (dry-run)
`goreleaser release`	`core ci --we-are-go-for-launch`

Configuration Migration

goreleaser:

builds:
  - main: ./cmd/app
    goos: [linux, darwin, windows]
    goarch: [amd64, arm64]

archives:
  - format: tar.gz
    files: [LICENSE, README.md]

release:
  github:
    owner: host-uk
    name: app

Core:

version: 1

project:
  name: app
  repository: host-uk/app

targets:
  - os: linux
    arch: amd64
  - os: darwin
    arch: arm64

publishers:
  - type: github

Key Differences

Separate build and release - Core separates core build from core ci
Safe by default - core ci is dry-run unless --we-are-go-for-launch
Simpler config - Fewer options, sensible defaults

From Manual Git Operations

Core automates multi-repo git workflows.

Manual	Core CLI
`cd repo1 && git status && cd ../repo2 && ...`	`core dev work --status`
Check each repo for uncommitted changes	`core dev health`
Commit each repo individually	`core dev commit`
Push each repo individually	`core dev push`

Example: Committing Across Repos

Manual:

cd core-php
git add -A
git commit -m "feat: add feature"
cd ../core-tenant
git add -A
git commit -m "feat: use new feature"
# ... repeat for each repo