No description
- Nix 65.5%
- Shell 34.5%
Atri Hegde
a588343ecb
t3-cli is the npm half of the same upstream release that t3code pins from GitHub Releases, so both updaters resolve their version from one tag and package.nix asserts the match at eval time. The published tarball ships no lockfile, so update.sh regenerates one and vendors it. Two upstream quirks are worked around: the manifest carries the monorepo's root `overrides` block, whose `parent>child` keys npm rejects outside that workspace, and prefetch-npm-deps fetches every lockfile entry regardless of os/cpu/libc, so the lock is pruned to the target platform. |
||
|---|---|---|
| .forgejo/workflows | ||
| pkgs | ||
| scripts | ||
| .gitignore | ||
| flake.lock | ||
| flake.nix | ||
| README.md | ||
edge-pkgs
Personal flake for fast-moving packages that should update independently of the main NixOS configuration.
Packages
cap-desktopclaude-codecodexhelium-browseropencode-desktopsynarat3-clit3codevibeyardzennotes
Usage
inputs.edge-pkgs = {
url = "git+ssh://git@forgejo.example.com/hegdeatri/edge-pkgs.git";
inputs.nixpkgs.follows = "nixpkgs";
};
Then install a package with:
inputs.edge-pkgs.packages.${pkgs.stdenv.hostPlatform.system}.claude-code
Updating
nix develop --command ./scripts/update-all.sh
nix flake check
Forgejo Actions runs the same updater on a schedule and commits changes when package pins change.
Forgejo Actions
The workflow expects a Forgejo runner label named nix. That label should point to a job image with Nix preinstalled.
For the existing medusa runner, this matches the registered label:
nix:docker://forgejo-nix-act:latest
Repository Actions must be enabled in Forgejo, and the workflow token needs permission to push commits back to the repository.