GitHub - Fusion/gogo: This is not a package manager.

gogo

What does it do?

A few examples: tldr, lazygit, lazysql, certinfo

But also tldr, lazysql, lazygit, croc, bit, viddy, up, fd, lsd, bat, fzf, rg, difft, certinfo, sops, age, gomuks, gotty, humanlog, jira, plow, pngsource, reflex, jq, gojq, jqp, mlr, fx, hugo, syncthing, minikube, dog, sd, navi, grex, zellij, xplr, gping, dust, dua, duf, xh, frp, rclone, etc.

Typical workflow

Installing:

1. Download the latest binary release for your OS
2. Rename it gogo and make sure it is in your path

Configuring:

1. Run gogo list and the path to your new configuration file will be provided
2. Recommended: update your Github token in config.toml

Packages list:

While gogo supports running directly against a Github repo (gogo <pkg> or gogo <user>/</pkg>), you should regularly update its list of pre-configured packages:

1. gogo refresh
2. gogo list

Getting help:

• gogo
• gogo fetch --help

etc.

Updating a single command:

1. Confirm command name: gogo list [-config <path-to-configuration>]
2. Run: gogo fetch <command-name> [-config <path-to-configuration>] -update

Installing missing commands:

1. Update configuration to include these commands
2. Run gogo fetch [-config <path-to-configuration>]

NOTE: As gogo's packages list grows, it seems like a bad idea to ask it to install every single package. Instead....

Installing from a personalized list:

Create a file of favorites, with a package name per line. For instance, chris_favs:

tldr
lazysql
lazygit
viddy
...

Run: gogo fetch @chris_favs

Obviously, replace chris_favs with the path to your own favorites file.

Refreshing all commands:

1. Run gogo fetch [-config <path-to-configuration>] -update

Specifying where the commands should go

If you leave this location unspecified, these commands will be located in the same directory as this tool itself.

To specify a different location, add to your configuration file/directory:

[paths]
targetdir = "<path>"

Where is that configuration file?

By default, it will be created in your user config directory, under gogo. You can specify a different location by running gogo -config <path>.

Working with GitHub's rate limiter

If you are running this tool as an anonymous user, you will be able to perform up to 60 queries per hour. If should be enough for many use cases.

If you need greater API allowance, follow this guide to create personal access tokens.

Note that you will need to grant your token specific repo access if you plan on getting commands from private repositories.

Store your token in the configuration file/directory:

[auth]
token = "github_<xxxxxxxxxx>"

Updating gogo itself

cp $(which gogo) $HOME/gogo.tmp && $HOME/gogo.tmp fetch Fusion/gogo -update && gogo refresh && rm -f $HOME/gogo.tmp

Development

Releasing

make && make package && chmod +x gogo-*
export RELEASE_TAG=<semantic-tag>
git tag v$RELEASE_TAG
git push --tags
gh release create v$RELEASE_TAG
gh release upload v$RELEASE_TAG gogo-darwin-arm64 gogo-linux-amd64 config.tgz
gh release edit v$RELEASE_TAG --draft=false --latest

TODO

• Use ldd to determine who's truly standalone
• Review tags because right now they are pretty weakly picked
• Parallel install
• SLSA 2
• Pick a version

FAQ

Please note that this FAQ mostly addresses issues that are out of my control.

Q: Why am I seeing a GLIBC error when I run some binaries?

A: This is a known issue. The binaries I fetch are built for more recent versions of glibc than the one you have. You can either build them yourself, or reach out to the maintainer of the project to build them for your architecture.

Q: Why am I seeing a message about libunwind?

A: This happens with some binaries that depend on libunwind. This is ok and the binaries are still fully functional. You can suppress this error by appending 2>/dev/null to your shell command. This is especially helpful if you are running a curses-based tool.