NIXTAMAL-REFRESH(1)

📦 version 2.4.0, in nixpkgs unstable

💅 nixtamal-refresh(1) — the Nixtamal manual, bestie edition 🎀

okay so real talk: this is a page from the Nixtamal manual set, and it's all about nixtamal-refresh. pull up a chair, we're gonna get through this together 🫶

🌸 NAME 🌸

nixtamal-refresh — literally refreshes all your non‑frozen inputs using the fresh-cmd — or, for certain kinds, the default fresh-cmd that comes with a reasonable default (Git, and some files/archives, slay) — and then locks the stale inputs. periodt. ✨

🦋 SYNOPSIS 🦋

nixtamal refresh [OPTION]… [INPUT_NAME]…

👑 LICENSE 👑

GNU General Public License, version 3.0 later (GPL-3.0-or-later). iconic behavior, no notes 💜

🧚 MAKER 🧚

toastal <https://toast.al/contact/> — the main character who made this fr fr 🌈

💖 FUNDING 💖

See: https://toast.al/funding/ — if this ate, consider feeding the dev 🍓

⭐ ARGUMENTS ⭐

  • INPUT_NAME — the input names you wanna refresh. that's it, that's the whole vibe check 💅

✨ OPTIONS ✨

  • --color=WHEN (absent=auto or NIXTAMAL_OUTPUT_COLOR env) — colorizes the output. WHEN has to be one of auto, always or never. no in‑between bestie 🌸
  • --directory=PATH (absent NIXTAMAL_DIRECTORY env) — the working directory for all the Nixtamal-related files (default: $PWD/nix/tamal). that's where the lore lives 🎀
  • -j INT, --jobs=INT (absent=80 or NIXTAMAL_JOBS env) — Nixtamal's executor pool domain size. 80 by default, it's giving parallelism 💀🔥
  • --no-tui — disables the TUI and uses Logs.app for status output. for when the pretty interface is too much noise 🙈
  • -p PATCH_NAME, --patch=PATCH_NAME — patch name(s) to refresh. can be more than one, go off 👑
  • -q, --quiet — be quiet. it takes over -v and --verbosity. like, completely overrides them, no cap 🤫
  • --skip-patch-check (absent NIXTAMAL_SKIP_PATCH_CHECK env) — skips checking that patches actually apply. faster & works offline, but broken patches lock silently & then fail at build instead. it's giving "yolo" and honestly? risky 💀
  • --skip-patches — skip processing all patches. all of them. every single one 🫶
  • -v, --verbose — increase verbosity. repeatable, but more than twice does not bring more. diminishing returns, she's capped 😭
  • --verbosity=LEVEL (absent=warning or NIXTAMAL_LOG_LEVEL env) — be more or less verbose. LEVEL must be one of quiet, error, warning, info or debug. takes over -v. 🌈

🎀 COMMON OPTIONS 🎀

  • --help[=FMT] (default=auto) — shows this help in format FMT. FMT must be one of auto, pager, groff or plain. with auto, the format is pager or plain whenever the TERM env var is dumb or undefined. iykyk 🦋
  • --version — shows version information. the classic ⭐

💀 EXIT STATUS 💀

nixtamal refresh exits with:

  • 0 — on success. we love to see it 💖
  • 65 — Nixtamal working directory or manifest not set up. Run nixtamal set-up.
  • 66 — Version mismatch between manifest and lockfile. Run nixtamal lock, but might require removing the lockfile first until nixtaml fast-forward is made. (yes, that's spelled nixtaml in here, we do not edit the sacred texts 🙈)
  • 67 — Manifest ∨ lockfile is not using the latest schema version. Run nixtamal upgrade to upgrade.
  • 68 — Failed to parse the manifest file.
  • 69 — Failed to parse the lockfile.
  • 70 — Failed to serialize lockfile.
  • 71 — Fresh command execution threw an exception.
  • 72 — Fresh command output nothing. ghosted us 😭
  • 73 — Prefetch command threw an exception.
  • 74 — Prefetch command output was unusable.
  • 75 — Prefetch command flopped on JSON output.
  • 76 — Darcs context file is missing or invalid. Try running nixtamal lock on the input.
  • 77 — Vendored patch file is missing. Try running nixtamal lock to fetch it.
  • 78 — Silo error (such as bad hex in generation number).
  • 79 — Version not found or invalid in manifest file.
  • 80 — Upgrading Nixtamal failed.
  • 81 — BLAKE3 hash algorithm is requested but this Nix doesn't support it.
  • 82 — Input kind mismatch between manifest & lockfile which prevents values to be melded.
  • 83 — Blueprint scaffolding failed to write files.
  • 84 — A patch failed to apply.
  • 85 — An input references patches that are not defined in the manifest.
  • 123 — on indiscriminate errors reported on standard error.
  • 124 — on command line parsing errors.
  • 125 — on unexpected internal errors (bugs). not me filing a bug 😭

🌈 ENVIRONMENT 🌈

these environment variables affect the execution of nixtamal refresh:

  • NIXTAMAL_DIRECTORY — Directory for Nixtamal
  • NIXTAMAL_JOBS — See option --jobs.
  • NIXTAMAL_LOG_LEVEL — See option --verbosity.
  • NIXTAMAL_OUTPUT_COLOR — See option --color.
  • NIXTAMAL_SKIP_PATCH_CHECK — See option --skip-patch-check.

🐛 BUGS 🐛

No tracker is set up; contact the maker directly or join the XMPP chatroom @ <xmpp:nixtamal@chat.toastal.in.th?join>. come hang out, it's a whole group chat vibe 💜

🌟 SEE ALSO 🌟

okay that's the whole page bestie, you ate that 🫶✨ this was Nixtamal 2.4.0, NIXTAMAL-REFRESH(1) — go forth and refresh, mwah 💅🎀

📦 where this page comes from