Search Results for "building"

Nunu is a CLI scaffolding tool for building Go applications; it aggregates and encapsulates popular Go ecosystem libraries to provide a modular, high‑performance, extensible foundation, complete with documentation and test support. Nunu is a scaffolding tool for building Go applications. Its name comes from a game character in League of Legends, a little boy riding on the shoulders of a Yeti.

A Go-based CLI tool for building, testing, and managing secure web applications.

Termenv is a Go library for building rich and portable terminal user interfaces with support for colors, styles, and advanced formatting. It provides abstractions that allow developers to write terminal output that adapts to the capabilities of different environments, ensuring consistent appearance across platforms. The library supports features such as true color, ANSI styling, and fallback mechanisms for terminals with limited capabilities.

...The tool is designed for efficiency, allowing users to perform operations quickly without relying on graphical interfaces. It supports authentication, configuration management, and API interactions, streamlining the process of building and deploying Lark-based applications. The CLI also facilitates automation by enabling scripting and integration with CI/CD workflows. It is particularly useful for teams that rely on Lark for communication and want to extend its functionality programmatically.

CFSSL is CloudFlare's PKI/TLS swiss army knife. It is both a command line tool and an HTTP API server for signing, verifying, and bundling TLS certificates. It requires Go 1.12+ to build. Note that certain linux distributions have certain algorithms removed (RHEL-based distributions in particular), so the golang from the official repositories will not work. Users of these distributions should install go manually to install CFSSL. You can set the GOOS and GOARCH environment variables to have...

Command line peer-to-peer data transfer tool based on libp2p. There already exists a long list of file transfer tools, so why bother building another one? The problem I had with the existing tools is that they rely on a limited set of servers to orchestrate peer matching and data relaying which poses a centralization concern. Many of the usual centralization vs. decentralization arguments apply here, e.g. the servers are single points of failure, the service operator has the power over whom to serve and whom not, etc. ...