lux-cli-help-upload(1)

🌸 NAME 🌸

lux-cli-help-upload — bestie, this is the one that generates a Lua rockspec for a Lux project and uploads it to the public luarocks repository. ✨

You can specify a source template for release and dev packages in the lux.toml. 🫶

Example:

[source]
url = "https://host.com/owner/$(PACKAGE)/refs/tags/$(REF).zip"
dev = "git+https://host.com/owner/$(PACKAGE).git"

You can use the following variables in the source template:

• $(PACKAGE): The package name.
• $(VERSION): The package version.
• $(REF): The git tag or revision (if in a git repository).
• You may also specify environment variables with $(<VAR_NAME>).

If the version is not set in the lux.toml, lux will search the current commit for SemVer tags and if found, will use it to generate the package version. 👑

---

✨ SYNOPSIS ✨

lux-cli help upload

---

💖 DESCRIPTION 💖

Okay so literally, generating a Lua rockspec for a Lux project and uploading it to the public luarocks repository is the whole gig. 💅 You can specify a source template for release and dev packages in the lux.toml — that's where the magic lives, no cap.

Example:

[source]
url = "https://host.com/owner/$(PACKAGE)/refs/tags/$(REF).zip"
dev = "git+https://host.com/owner/$(PACKAGE).git"

You can use the following variables in the source template:

• $(PACKAGE): The package name. 🎀
• $(VERSION): The package version. 🌸
• $(REF): The git tag or revision (if in a git repository). 🦋
• You may also specify environment variables with $(<VAR_NAME>). 🔥

Heads up bestie: if the version is not set in the lux.toml, lux will search the current commit for SemVer tags and if found, will use it to generate the package version. That's the fallback, iykyk. 💜

---

That's the whole page, fr fr — the footer's just vibing down there with upload on one side and lux-cli-help-upload(1) on the other, hanging out under the General Commands Manual banner (and ngl the date slot is literally empty, so we're not gonna pretend otherwise 🫶). Mwah, go ship something iconic. 💅✨🎀