Installer goctl avec Homebrew, Nix

Liens du projet

• Page d'accueil
• Dépôt
• Docs amont
• Page du gestionnaire de paquets

Commandes et alias

• goctl

Historique du projet

The go-zero repository was created in August 2020. Its README says the framework grew from an early 2018 transition from a Java and MongoDB monolith to Go microservices, with goctl serving as the code-generation tool around go-zero's API description syntax.

goctl evolved as a tool module inside the go-zero repository. Official documentation describes it as go-zero's code generation tool for HTTP services, gRPC services, models, Dockerfiles, Kubernetes manifests, and related workflow tasks.

Historique d'adoption

go-zero became a large Go framework project, with GitHub repository metadata showing more than thirty thousand stars by June 2026. goctl's adoption is tied to that framework: users installing go-zero for API and RPC services also install goctl to generate the boilerplate that keeps services consistent.

Distribution follows both Go and package-manager norms. The official README documents `go install github.com/zeromicro/go-zero/tools/goctl@...`, Homebrew installation with `brew install goctl`, and a Docker image path.

Modes d'utilisation

Typical usage begins by creating a `.api` file, running `goctl api go -api ... -dir ...`, and then running the generated Go service. The README's quick start shows goctl generating handler, logic, config, service-context, and type files for an HTTP API.

The CLI reference groups goctl commands around API generation, RPC generation, model generation, Docker, Kubernetes, environment checks, config, templates, naming style, Swagger, upgrades, migration, shell completion, and bug reporting.

Pourquoi les passionnés de paquets s'y intéressent

Package nerds care about goctl because it is a generator packaged separately from the framework it serves. That split lets a team pin or install the CLI through Homebrew, Go tooling, or Docker while generated services depend on normal Go modules.

It is also a good example of spec-driven development in a package ecosystem: the `.api` file becomes a compact source artifact, and goctl expands it into a repeatable service layout.

Chronologie

• 2018: go-zero's README describes the internal microservices transition that motivated the framework.
• 2020-08: go-zero GitHub repository created.
• 2025-10: goctl v1.9.2 release tag published under tools/goctl.
• 2026-02: goctl v1.10.0 release tag published.
• 2026-03: goctl v1.10.1 release tag published.

Related projects

• go-zero is the framework goctl serves.
• Protocol Buffers and gRPC are part of the RPC generation workflow.
• mcp-zero, ai-context, and zero-skills are related go-zero projects for AI-assisted framework-compliant development.

Sources

• https://api.github.com/repos/zeromicro/go-zero
• https://api.github.com/repos/zeromicro/go-zero/releases
• https://github.com/zeromicro/go-zero
• https://github.com/zeromicro/go-zero/releases
• https://go-zero.dev/getting-started/
• https://go-zero.dev/reference/cli-guide/