LIGHTYENABLEMOD(1)

💅 lighty-enable-mod / lighty-disable-mod — bestie edition

okay so this is the General Commands Manual page for lighty-enable-mod and lighty-disable-mod, no cap. Two little icons that turn config on and off inside the lighttpd server. Let's get into it 🎀

---

✨ NAME ✨

lighty-enable-mod, lighty-disable-mod — enable or disable configuration in lighttpd server 🦋

---

🌸 SYNOPSIS 🌸

lighty-enable-mod [module]
lighty-disable-mod [module]

---

💖 DESCRIPTION 💖

This manual page documents, briefly, the lighty-enable-mod and lighty-disable-mod commands. Like, briefly briefly. We're not writing a novel here.

lighty-enable-mod and lighty-disable-mod are programs that enable (and respectively disable) the specified configuration file within lighttpd configuration. That's the whole job. That's the vibe.

Both programs can be run interactively or from the command line, your choice, main character energy either way ✨ If either program is called without any arguments, an input prompt pops up for the user, where he might choose among available lighttpd modules. And if a module name was given on the command line? Immediate action is taken. No waiting, no small talk, periodt 💅

---

🫶 EXIT STATUS 🫶

Both programs indicate failure in their exit status. lighty-enable-mod or lighty-disable-mod respectively may leave execution with one of the following exit codes:

• 0 — denotes success 👑 (slay)
• 1 — denotes a fatal error (e.g., a module could not be enabled, or a dependency was not found) 💀
• 2 — denotes a minor flaw (e.g., a module was not enabled because it was already loaded before) 🙈

⭐ Note ⭐

You can (un-)load several modules at a time. The exit status will only reflect the most serious issue — where a minor flaw beats no error, but a fatal error beats a minor flaw. Which means: if a minor flaw was encountered as well as a fatal error, the program will leave with exit status 1 and stop immediately. It said nope, we're done here. 😭

---

🧚 DEPENDENCIES 🧚

Debian allows lighttpd modules to formulate dependencies to other modules they depend on. It's giving "you can't sit with us unless you brought your friends."

Configuration files are scanned for dependencies upon load or unload of modules, not at runtime of the web server. So it's a load-time thing, not a live thing. iykyk.

Such a magic line has the following format:

# -*- depends: module[, module] -*-

and may appear anywhere in the file. Literally anywhere. It's not picky.

If such a line is found, the extracted name is interpreted as a dependency to another lighttpd module. lighty-enable-mod will seek available configurations to satisfy this dependency and will recursively enable all dependencies found on its way. And lighty-disable-mod will disable reverse dependencies recursively. It goes all the way down, bestie. 🌀

---

🔥 SEE ALSO 🔥

• lighttpd(1)

---

💜 AUTHOR 💜

Program and man pages were originally written by Krzysztof Krzyżaniak <eloy@debian.org> and later modified by Arno Töll <debian@toell.net>. Legends, honestly. Thank you for your service 🫶

---

and that's the whole page, bestie!! 🌈 this version is dated 2006-01-11 and it lives under the name LIGHTYENABLEMOD(1) — go enable something iconic 💅✨