Search Results for "setup-1 bin"

Networking plugin repository for pod networking in Kubernetes using Elastic Network Interfaces on AWS. Launch kubelet with network plugins set to cni (--network-plugin=cni), the cni directories configured (--cni-config-dir and --cni-bin-dir) and node ip set to the primary IPv4 address of the primary ENI for the instance (--node-ip=$(curl http://169.254.169.254/latest/meta-data/local-ipv4)). It is also recommended that you set --max-pods equal to (the number of ENIs for the instance type × (the number of IPs per ENI - 1)) + 2; for details, see vpc_ip_resource_limit.go. ...

...Dotenv load variables from a .env file into ENV when the environment is bootstrapped. It can be used as a library (for loading in env for your own daemons etc) or as a bin command. There is test coverage and CI for both linuxish and windows environments, but I make no guarantees about the bin version working on windows. Existing envs take precedence of envs that are loaded later.

gon is a simple, no-frills tool for signing and notarizing your CLI binaries for macOS. gon is available as a CLI that can be run manually or in automation pipelines. It is also available as a Go library for embedding in projects written in Go. gon can sign and notarize binaries written in any language. Beginning with macOS Catalina (10.15), Apple is requiring all software distributed outside of the Mac App Store to be signed and notarized. Software that isn't properly signed or notarized...

A terminal based graphical activity monitor inspired by gtop and vtop. Working and tested on Linux, FreeBSD and macOS. Windows support is planned. OpenBSD works with some caveats. Clone the repo and then run scripts/download.sh to download the correct binary for your system from the releases tab. gotop ships with a few colorschemes which can be set with the -c flag followed by the name of one. You can find all the colorschemes in the colorschemes folder.

Plugin for presenting an IPFS gateway over i2p. This is only the gateway part, A.K.A. the easy part. It will make your IPFS gateway accessible via i2p clients, but it will not route communication between IPFS nodes over i2p(1). This means that it doesn't make your IPFS instance anonymous, it just makes it accssible to clients anonymously(2). It simply takes advantage of the plugin system to set up some hidden services when the IPFS plugin is initialized. It does this by reading the IPFS...