lux-cli-dist-help(1)

💖 the lux-cli-dist-help glow-up 💖

okay bestie, welcome to the General Commands Manual page for lux-cli-dist-help(1) — yes, it's the manual page for the help command, and the meta of it all is honestly iconic. 🫶

---

✨ NAME ✨

lux-cli-dist-help — prints this message, or the help of the given subcommand(s). It's giving “help me help you” in the most useful way. 💅

---

🌸 SYNOPSIS 🌸

lux-cli dist help [subcommands]

---

🦋 DESCRIPTION 🦋

This command prints this message, or the help of the given subcommand(s). That's the whole assignment, and it ate. ✨

---

🎀 SUBCOMMANDS 🎀

Here's the little subcommand fam, each with its own manual-page energy:

📦 lux-cli-dist-help-flat-archive(1)

This one distributes an archive of a flat install tree that includes all dependencies.

The resulting archive does not include the etc directory or build dependencies.

Unlike a Lux tree, dependency conflicts are not supported/handled — so don't come for it with conflict drama, bestie. 😭

🧚 lux-cli-dist-help-bin(1)

This compiles a Lux project, including its dependencies, into a single binary, which runs on systems that do not have Lua installed.

Projects with native Lua modules are not single binaries: the modules are copied as shared libraries next to the output binary, and must be shipped alongside it.

As with flat-archive, dependency conflicts are not supported/handled.

The entrypoint is specified via the lux.toml's [run] field, e.g.:

[run]
args = ["src/main.lua"]

🫶 lux-cli-dist-help-help(1)

Prints this message or the help of the given subcommand(s). Yes, helpception, and we're obsessed. 💖

---

Footer sign-off: source/version vibes are help and lux-cli-dist-help(1); the original doesn't hand us a date, so no invented date, bestie — periodt. 💅✨