Gorilla

Munki-like Application Management for Windows

Gorilla is intended to provide application management on Windows using Munki as inspiration. Gorilla supports .msi, .ps1, .exe, or .nupkg (via chocolatey).

Getting Started

Information related to installing and configuring Gorilla can be found on the Wiki. For quick manual-test setup helpers on a fresh Windows VM, see utils/manual-test/README.md.

Building

If you just want the latest version, download it from the releases page.

Building from source requires the Go tools.

macOS and Linux

After cloning this repo, just run make build. A new binary will be created in build/

Windows

After cloning this repo, just run go build -i ./cmd/gorilla. A new binary will be created in the current directory.

Contributing

Pull requests are welcome. The Makefile provides the same validation entry points used by CI:

make verify
    Portable Go + .NET validation expected before pushing.

make verify-windows
    Windows build and source integration validation.

make verify-e2e
    Windows validation plus the current FlaUI UI suite.

make verify-release GORILLA_RELEASE_EXE=<path>
    Current released-binary integration plus the lower validation layers.

Use smaller targets such as make go-test, make go-staticcheck, make ui-lint, or make ui-test while iterating. See AGENTS.md and make help for the complete validation contract and guidance on which level applies to a change.

Repo Admin Mode

Gorilla also supports local repo admin workflows:

• -b / -build: compile packages-info/*.yaml files into catalog files under catalogs/
• -i / -import: scaffold package-info data from an installer (currently stubbed as not yet implemented)

For these modes, set repo_path in config (or run from your repo root so the current working directory is used). See examples/example_package-info.yaml for a package-info example.