https://github.com/fusion/gogo
This is not a package manager.
https://github.com/fusion/gogo
Last synced: 8 months ago
JSON representation
This is not a package manager.
- Host: GitHub
- URL: https://github.com/fusion/gogo
- Owner: Fusion
- License: apache-2.0
- Created: 2024-10-06T21:27:34.000Z (over 1 year ago)
- Default Branch: main
- Last Pushed: 2025-02-08T22:25:03.000Z (over 1 year ago)
- Last Synced: 2025-09-10T00:21:08.076Z (9 months ago)
- Language: Go
- Size: 15.1 MB
- Stars: 5
- Watchers: 1
- Forks: 1
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
## gogo
### What does it do?
Here is why I wrote this tool: I love the idea of being able to roll out my favorite shell tools locally anywhere I need to.
This means I am a fan of self-sufficient tools, such as lazygit and others. No library dependencies, and as OS-independent as possible.
So, please **do not call this tool a package manager** as that is a non-goal.
All it does is, provided a minimal list of hints, it will download and install whatever commands I need:
- as long as there are no dependencies
- as long as they are available as packages on github
A few examples:
[tldr](https://github.com/isacikgoz/tldr), [lazygit](https://github.com/jesseduffield/lazygit), [lazysql](https://github.com/jorgerojas26/lazysql), [certinfo](https://github.com/pete911/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](https://github.com/Fusion/gogo/releases) 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 ` or `gogo /`),
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 ]`
2. Run: `gogo fetch [-config ] -update`
#### Installing missing commands:
1. Update configuration to include these commands
2. Run `gogo fetch [-config ]`
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 ] -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 = ""
```
### 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 `.
### 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](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens) 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_"
```
### 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=
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.