On 2025-09-16 01:21, Carlo Zancanaro wrote:
Hi Jake,
I don't know much about the overall Lua situation, but I seem to have
Prosody working by using the plugin-paths configuration parameter. This
seems to pass straight through to Prosody's plugin_paths configuration
parameter[1 [1]].
My configuration starts like this:
--8<---------------cut here---------------start------------->8---
(prosody-configuration
(modules-enabled (cons* "mam" "csi_simple" "smacks"
%default-modules-enabled))
(plugin-paths (list prosody-http-upload prosody-smacks
prosody-vcard-muc))
...)
--8<---------------cut here---------------end--------------->8---
Then I define my components with appropriate plugin and/or
modules-enabled as they need.
I hope that helps.
Carlo
[1]: https://prosody.im/doc/plugins_directory
Yep, that seems to have worked, thanks! Looks like some G-exp magic.
Still can't seem to get Lua packages working right- adding them to the
profile doesn't result in Prosody seeing them, but for now I'm using
input rewriting to add them as inputs to my Prosody package, which seems
to be working with `lua5.2-ossl`- even though it's a propagated input
for `prosody-cloud-notify-encrypted`, it doesn't get found without this
workaround. If anyone's got other ideas or techniques I'd greatly
appreciate it.
Thanks again for the help!
Jake
Links:
------
[1] https://prosody.im/doc/plugins_directory
