Add GO_PROD=1 production build mode to go-workflow

When GO_PROD=1 is set at runtime, go build receives -trimpath and
-ldflags="-s -w" to strip source paths, symbol tables, and DWARF debug
info from compiled binaries. Applied to go build only — go test is
unaffected so stack traces remain readable during development.
Usage: docker run --env GO_PROD=1 --rm -v "$(pwd)":/app casjaysdev/go
- rootfs/usr/local/bin/go-workflow: add BUILD_FLAGS array populated when
GO_PROD=1; pass flags to go build step only; print mode notice when active

rootfs/usr/local/bin/go-workflow
This commit is contained in:
2026-06-21 09:51:21 -04:00
parent 7ce3d79aba
commit 373136fead
+13 -1
View File
@@ -29,6 +29,18 @@ run_step() {
echo ""
}
# Production mode: GO_PROD=1 strips binaries and removes local source paths.
# Enabled via: docker run --env GO_PROD=1 ...
# -trimpath removes all local file system paths from the compiled binary
# -ldflags=-s strips the symbol table; -w strips DWARF debug info
# Both reduce binary size and avoid leaking build-host paths into the output.
# Applied to go build only — not go test — so stack traces stay readable.
BUILD_FLAGS=()
if [ "${GO_PROD:-0}" = "1" ]; then
echo " (production mode: -trimpath -ldflags=-s -w)"
BUILD_FLAGS=(-trimpath -ldflags="-s -w")
fi
# 1. Sync module graph and go.sum before anything reads them
run_step "go mod tidy" go mod tidy
# 2. Format all Go source files in place
@@ -38,7 +50,7 @@ run_step "go vet ./..." go vet ./...
# 4. Run tests — fail fast before wasting time on a build
run_step "go test ./..." go test ./...
# 5. Build all main packages; output lands alongside source in each package dir
run_step "go build ./..." go build ./...
run_step "go build ./..." go build "${BUILD_FLAGS[@]}" ./...
echo "✅ Done."