nix3-registry-add(1)

πŸ’… nix3-registry-add ✨

okay so bestie, you found the page for nix registry add, straight outta the General Commands Manual. It's giving flake-registry glow-up energy and honestly? iconic. Let's go 🫢

⚠️ Warning β€” This program is experimental and its interface is subject to change. Not me warning you twice: it's literally in the original. Don't get too attached to the exact flags, bestie, they might shift. πŸ’€

🌸 Name

nix registry add β€” add/replace a flake in the user flake registry πŸŽ€


✨ Synopsis

nix registry add [option…] from-url to-url

πŸ¦‹ Examples

  • Set the nixpkgs flake identifier to a specific branch of Nixpkgs:
# nix registry add nixpkgs github:NixOS/nixpkgs/nixos-20.03
  • Pin nixpkgs to a specific revision:
# nix registry add nixpkgs github:NixOS/nixpkgs/925b70cd964ceaedee26fde9b19cc4c4f081196a
  • Add an entry that redirects a specific branch of nixpkgs to another fork:
# nix registry add nixpkgs/nixos-20.03 ~/Dev/nixpkgs
  • Add nixpkgs pointing to github:nixos/nixpkgs to your custom flake registry:
nix registry add --registry ./custom-flake-registry.json nixpkgs github:nixos/nixpkgs

πŸ‘‘ Description

Lowkey the whole point: this command adds an entry to the user registry that maps the flake reference from-url to the flake reference to-url. And if an entry for from-url already exists? It gets overwritten. No warning, no asking, just replaced. Slay but also be aware. ✨

Entries can be removed using nix registry remove. 🧹


πŸ’… Options

  • --registry registry β€” The registry to operate on.

πŸŽ€ Common evaluation options

  • --arg name expr β€” Pass the value expr as the argument name to Nix functions.
  • --arg-from-file name path β€” Pass the contents of file path as the argument name to Nix functions.
  • --arg-from-stdin name β€” Pass the contents of stdin as the argument name to Nix functions.
  • --argstr name string β€” Pass the string string as the argument name to Nix functions.
  • --eval-store store-url β€” The URL of the Nix store to use for evaluation, i.e. to store derivations (.drv files) and inputs referenced by them.
  • --impure β€” Allow access to mutable paths and repositories.
  • --include, -I path β€” Add path to search path entries used to resolve lookup paths.

This option may be given multiple times.

Paths added through -I take precedence over the nix-path configuration setting and the NIX_PATH environment variable. πŸ†

  • --override-flake original-ref resolved-ref β€” Override the flake registries, redirecting original-ref to resolved-ref.

  • --debug β€” Set the logging verbosity level to β€˜debug’.
  • --log-format format β€” Set the format of log output; one of raw, internal-json, bar or bar-with-logs.
  • --print-build-logs, -L β€” Print full build logs on standard error.
  • --quiet β€” Decrease the logging verbosity level.
  • --verbose, -v β€” Increase the logging verbosity level.

⭐ Miscellaneous global options

  • --help β€” Show usage information.
  • --offline β€” Disable substituters and consider all previously downloaded files up-to-date.
  • --option name value β€” Set the Nix configuration setting name to value (overriding nix.conf).
  • --refresh β€” Consider all previously downloaded files out-of-date.
  • --repair β€” During evaluation, rewrite missing or corrupted files in the Nix store. During building, rebuild missing or corrupted store paths.
  • --version β€” Show version information.
πŸ“ Note β€” See man nix.conf for overriding configuration settings with command line flags.

And that's the whole thing, bestie. You ate. πŸ“ This was nix3-registry-add(1) from the General Commands Manual β€” the footer line says nix3-registry-add(1) too, so the page is lowkey bookended by its own name, which is honestly a vibe. πŸ’œ Go forth and pin your flakes. No cap. πŸ’–βœ¨

πŸ“¦ where this page comes from