Welcome to this instance of Nixery, an ad-hoc container image registry that provides packages from the Nix package manager.
You can pull container images from this registry
at nixery.dev by appending any
packages that you need in the URL, separated by slashes.
These usage examples assume that you use Docker, but should not be much different for other OCI-compatible platforms.
Pull an image from this registry, separating each package you want included by a slash:
docker pull nixery.dev/shell/git/htop
This gives you an image with git, htop and an interactively
configured shell. You could run it like this:
docker run -ti nixery.dev/shell/git/htop bash
Each path segment corresponds either to a key in the Nix package set, or a meta-package that automatically expands to several other packages.
Meta-packages must be the first path component if they are used. Currently there are only two meta-packages:
shell, which provides a bash-shell with interactive
configuration and standard tools like coreutils
arm64, which provides ARM64 binaries
The short version is that we use the Nix package manager and an optimised layering strategy.
Check out the Nixery talk from NixCon 2019 for more information.
nixery.dev in production?
While we appreciate the enthusiasm, if you would like to use Nixery in your production
project we recommend setting up a private instance. The public Nixery
at nixery.dev is run on a best-effort basis and we make no guarantees
about availability.
Nixery was written by tazjin, originally at Google. These days Nixery is maintained by TVL.
Nixery would not be possible without the many people that have contributed to Nix and nixpkgs over time, maybe you could become one of them?
Nixery lives in the TVL monorepo. All development happens there and follows the TVL contribution guidelines.
We mirror the source code to Github but do not guarantee that anyone will look at PRs or issues there.