diff options
author | Vincent Ambo <mail@tazj.in> | 2022-06-16T14·52+0300 |
---|---|---|
committer | clbot <clbot@tvl.fyi> | 2022-06-16T15·08+0000 |
commit | ac10907913b713403194021c1d68cb34a1d68a19 (patch) | |
tree | 51b83c80bee27666a74d704d0db660f1c53248d5 /tools/nixery/docs/src | |
parent | 15a9aad6584e7922dbff029f9eebaa1928ea99c5 (diff) |
docs(nixery): dynamically display current nixpkgs commit r/4241
People occasionally ask what the current nixpkgs commit is on nixery.dev (see e.g. https://github.com/tazjin/nixery/issues/153). With this change, the commit is displayed on nixery.dev if Nixery is built for the TVL deployment. Change-Id: I795220214db5a367a126c9b4bd03754e9f144940 Reviewed-on: https://cl.tvl.fyi/c/depot/+/5881 Reviewed-by: sterni <sternenseemann@systemli.org> Tested-by: BuildkiteCI Autosubmit: tazjin <tazjin@tvl.su>
Diffstat (limited to 'tools/nixery/docs/src')
-rw-r--r-- | tools/nixery/docs/src/nixery.md | 10 |
1 files changed, 1 insertions, 9 deletions
diff --git a/tools/nixery/docs/src/nixery.md b/tools/nixery/docs/src/nixery.md index d9ba179010f6..0d55cfb545d9 100644 --- a/tools/nixery/docs/src/nixery.md +++ b/tools/nixery/docs/src/nixery.md @@ -34,7 +34,7 @@ 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 +- `shell`, which provides a `bash`-shell with interactive configuration and standard tools like `coreutils`. - `arm64`, which provides ARM64 binaries. @@ -53,14 +53,6 @@ Over [on Github][Nixery]. It is licensed under the Apache 2.0 license. Consult the documentation entries in the sidebar for information on how to set up your own instance of Nixery. -### Which revision of `nixpkgs` is used for the builds? - -The instance at `nixery.dev` tracks a recent NixOS channel, currently NixOS -20.09. The channel is updated several times a day. - -Private registries might be configured to track a different channel (such as -`nixos-unstable`) or even track a git repository with custom packages. - ### Should I depend on `nixery.dev` in production? While we appreciate the enthusiasm, if you would like to use Nixery in your |