lux-cli-update(1)

💖 lux-cli-update(1) — General Commands Manual, but make it cute ✨

Okay so this is the General Commands Manual page for lux-cli-update, and it is literally all about updating every rock in a project. Bestie, we're going flag by flag, no cap. 🫶

🌸 NAME 🌸

lux-cli-update — updates all rocks in a project. That's the whole assignment. Periodt. 💅

✨ SYNOPSIS ✨

lux-cli update [--no-integrity-check] [-b|--build] [--server]
[--extra-servers] [-t|--test] [--namespace] [-p|--package] [--lua-dir]
[--lua-version] [--tree] [--cache-dir] [--data-dir] [--variables]
[--profile] [--verbose] [--no-progress] [--no-prompt] [--preset]
[--nvim] [--no-tfa] [--timeout] [--max-jobs] [--no-luarc]
[--no-wrap-bin] [--user-agent] [-h|--help] [PACKAGES]

🌈 DESCRIPTION 🌈

Updates all rocks in a project. Yep, that's the vibe. Main character energy only. 👑

🔥 OPTIONS 🔥

• --no-integrity-check — Skip the integrity checks for installed rocks when syncing the project lockfile. Do not skip this casually, bestie.
• -b, --build <BUILD> — Build dependencies to update. Also called dev. When updating a project, these must be package names.
• --server <server> — Fetch rocks/rockspecs from this server (takes priority over config file).
• --extra-servers <extra-server> — Fetch rocks/rockspecs from these servers in addition to the main server{n} (overrides any entries in the config file).
• -t, --test <TEST> — Build dependencies to update. When updating a project, these must be package names.
• --namespace <namespace> — Specify the luarocks server namespace to use.
• -p, --package <PACKAGE> — Project to modify.
• --lua-dir <prefix> — Specify the directory in which to install Lua if not found.
• --lua-version <ver> — Which Lua installation to use. {n} Valid versions are: '5.1', '5.2', '5.3', '5.4', '5.5', 'jit' and 'jit52'. {n} If not set, Lux will attempt to detect the Lua version: {n}
  • From the current project, if it has an exact Lua version requirement. {n}
  • From the Lua installation that is available on the PATH.
• --tree <tree> — Which tree to operate on. {n} In a workspace, this can be used to specify a detached workspace tree.
• --cache-dir <cache-dir> — Specifies the cache directory, e.g. for luarocks manifests.
• --data-dir <data-dir> — Specifies the data directory, {n} in which the default user install tree resides {n} (e.g. ~/.local/share/lux).
• --variables <variable> — Override config variables. {n} Example: lx -v "LUA=/path/to/lua" ...
• --profile <profile> — The build profile to use when compiling packages. {n} Default: release
  • Possible values:
    • release
    • dev
• --verbose — Display verbose output of commands executed, enabling DEBUG logs. {n} To enable TRACE logs, set RUST_LOG=trace
• --no-progress — Don't print any progress bars or spinners.
• --no-prompt <NO_PROMPT> — Skip prompts, selecting the default option. {n} Prompting is enabled by default in terminal/TTY environments.
  • Possible values:
    • true
    • false
• --preset <preset> — Configure Lux for a specific environment. {n} Valid presets are: 'nvim'
  • Possible values:
    • nvim: Configure Lux for Neovim plugins
• --nvim — [DEPRECATED] Configure lux for installing Neovim packages. {n} Use --preset nvim instead.
• --no-tfa — Disable prompts for two-factor authentication (2FA) codes. {n} It is strongly recommended to enable 2FA instead see (https://luarocks.org/settings/two-factor-auth).
• --timeout <seconds> — Timeout on network operations, in seconds. {n} 0 means no timeout (wait forever). Default is 30.
• --max-jobs <MAX_JOBS> — Maximum buffer size for parallel jobs, such as downloading rockspecs and installing rocks. 0 means no limit. Default is 0.
• --no-luarc — Do not generate or update a .luarc.json file when building {n} a project.
• --no-wrap-bin — Do not wrap Lua bin scripts.
• --user-agent <USER_AGENT> — The user agent to set when making web requests. Default is "lux/<version>".
• -h, --help — Print help (see a summary with '-h').
• [PACKAGES] — Packages to update. When updating a project, these must be package names.

xoxo, bestie 💖 — this has been lux-cli-update(1) from the General Commands Manual, and the footer energy is source/version update + lux-cli-update(1) (date? not on this page, so no date to report 🎀). Go slay those rocks. 💅✨