# 08 — Build & Release ## CLI flags Defined in `cmd/logpile/main.go`: | Flag | Default | Purpose | |------|---------|---------| | `--port` | `8082` | HTTP server port | | `--file` | empty | Preload archive file | | `--sanitize` | empty | De-identify customer data in this file and exit (`docs/log-sanitization.md`) | | `--sanitize-out` | empty | Where `--sanitize` writes its result (default: overwrite the input) | | `--version` | `false` | Print version and exit | | `--no-browser` | `false` | Do not auto-open browser | | `--hold-on-crash` | `true` on Windows | Keep console open after fatal crash | ## Common commands ```bash make build make build-all make test make fmt ``` Notes: - `make build` outputs `bin/logpile` - `make build-all` builds the supported cross-platform binaries ## Private module dependency logpile depends on `git.mchus.pro/reanimator/parser/v20` (archive parsing, Redfish replay/analysis, `models`, `pciids` — see ADL-080 in `10-decisions.md`), a private Gitea host. `git.mchus.pro` has no public Go checksum database entry, so a clean module cache needs `GOPRIVATE=git.mchus.pro/*` set before `go mod tidy`/`go build`/`go get` can resolve it (`go env -w GOPRIVATE=git.mchus.pro/*`), or a `go.sum` seeded from another project that already depends on the same version. This is logpile's first non-replaced external Go module dependency — CI must set `GOPRIVATE` accordingly. PCI vendor/device ID data (`pci.ids`) now lives inside that module; logpile no longer embeds its own copy or carries the `third_party/pciids` submodule. ## Release script Run: ```bash ./scripts/release.sh ``` Current behavior: 1. Reads version from `git describe --tags` 2. Refuses a dirty tree unless `ALLOW_DIRTY=1` 3. Sets stable Go cache/toolchain environment 4. Creates `releases/{VERSION}/` 5. Creates a release-notes template if missing 6. Builds `darwin-arm64` and `windows-amd64` 7. Packages any already-present binaries from `bin/` 8. Generates `SHA256SUMS.txt` Release tag format: - project release tags use `vN.M` - do not create `vN.M.P` tags for LOGPile releases - release artifacts and `main.version` inherit the exact git tag string Important limitation: - `scripts/release.sh` does not run `make build-all` for you - if you want Linux or additional macOS archives in the release directory, build them before running the script Toolchain note: - `scripts/release.sh` defaults `GOTOOLCHAIN=local` to use the already installed Go toolchain and avoid implicit network downloads during release builds - if you intentionally want another toolchain, pass it explicitly, for example `GOTOOLCHAIN=go1.24.0 ./scripts/release.sh` ## Run locally ```bash ./bin/logpile ./bin/logpile --port 9090 ./bin/logpile --no-browser ./bin/logpile --version ``` ## macOS Gatekeeper ```bash xattr -d com.apple.quarantine /path/to/logpile-darwin-arm64 ```