Comment a link on a pull request that boots what it built, in the
reviewer's browser.
The action names the store paths a flake attribute produces and posts a
trynix.dev link that mounts them in an x86_64 VM
running in the tab. A reviewer clicks it and gets a shell with the
branch's build on PATH. There is no server and nothing to install.
- uses: cachix/cachix-action@v17
with:
name: my-cache
authToken: ${{ secrets.CACHIX_AUTH_TOKEN }}
- run: nix build .#my-package
- uses: fzakaria/trynix@v1
with:
cache: https://my-cache.cachix.org
publicKey: my-cache.cachix.org-1:0Ma9…
attrs: .#my-packageIt publishes nothing of its own. Whatever already fills your cache keeps
doing it, and the action hands that cache's URL and public key to the
browser, so cachix, attic, an S3 bucket and a directory of narinfos on a
static host are all the same thing to it. It holds no token.
Packages and flake apps both work, several boot together in one VM, and
the comment is edited in place rather than repeated on every push. Pull
requests from forks are supported and
documented,
including what giving a fork's build a push token costs.
Options and example workflows.
This release tracks v1: the tag moves as the action changes and these
notes are updated in place, so there is one version to point at.