hermit
hermit copied to clipboard
cashapp
🐚 Hermit manages isolated, self-bootstrapping sets of tools in software projects.
This is even if the previously synced private repo contains manifests overwriting the ones in the public repo
If a package was removed from the manifests for some reason, we should still be able to uninstall it from the environment. Now, we are getting a package not found...
After creating the `go@tip` channel, Hermit updated it once on Dec 2 but has not updated it since, even though there are more recent builds available. Here is the DB...
I have not dug into this at all, but it appears that we could use a [GitHub App + user-to-server + short-lived tokens](https://docs.github.com/en/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps) to achieve this.
Something is failing somewhere, but the underlying error gets swallowed and all the user sees is: ``` fatal: failed to download from any of ... ``` Looking at the [code](http://github.com/cashapp/hermit/blob/c0adb69c60738ea1818235c3ebaec093bb43cda9/cache/cache.go#L109-L127)...
eg. ``` 🐚~/Projects/shreq $ hermit info --json $(hermit list -s) | jq '.[].Binaries' [ "bin/*" ] ```
A good point was brought up in the [announcement post on Lobsters](https://lobste.rs/s/leqj8z/hermit_manages_isolated_self#c_fnsgz8) - that while Hermit solves consistent tooling across workstation and CI, it doesn't for deploys. I suggested a...
There are a couple of cases where various approaches to this would be useful: A conservative approach might be to just allow versions to be merged, though this could get...
We should check that at least some of the `source` references in the new release are available before creating a new release. For example releases 2.7.0 - 3.1.0 in https://github.com/pressly/goose/releases/...
We could have something like `HERMIT_CHANNEL_FREQUENCY_OVERRIDE=15m` to override the sync frequency in CI so that changes would take effect faster, making it easier to roll out fixes in the CI.