Change Details

**Feature summary**: A hook or hooks added to Scribunto's `require` resolution that lets you (1) locate the module yourself; (2) load its contents yourself; (3) aborting further hooks from running. **Use case(s)**: On wiki farms where many wikis share a single server, a centralized code repository wiki is better off serving code via DB than over HTTP. For the most part, this functionality can be developed independently of Scribunto, but Scribunto would need hook support. **Benefits**: This will give wiki farms greater flexibility over how to configure Scribunto without any need to fork the extension.

**Feature summary**: A hook or hooks added to Scribunto's `require` resolution that lets you (1) locate the module yourself; (2) load its contents yourself; (3) aborting further hooks from running. **Use case(s)**: On wiki farms where many wikis share a single server, a centralized code repository wiki is often used with a custom config, sharing code either via DB or over HTTP. For the most part, this functionality can be developed independently of Scribunto, but Scribunto would need hook support. **Benefits**: This will give wiki farms greater flexibility over how to configure Scribunto without any need to fork the extension.

**Feature summary**: A hook or hooks added to Scribunto's `require` resolution that lets you (1) locate the module yourself; (2) load its contents yourself; (3) aborting further hooks from running. **Use case(s)**: On wiki farms where many wikis share a single server, a centralized code repository wiki is better off servoften used with a custom config, sharing codee either via DB thanor over HTTP. For the most part, this functionality can be developed independently of Scribunto, but Scribunto would need hook support. **Benefits**: This will give wiki farms greater flexibility over how to configure Scribunto without any need to fork the extension.