# HG changeset patch # User João Duarte # Date 1563990208 25200 # Node ID d145eb696475415eb336c5508db0caebd7e62998 # Parent 661feb336e1848f736e6a739fe70b5562f441bd1 prosodyctl: The install command now performs its job at a dedicated folder for custom plugins diff -r 661feb336e18 -r d145eb696475 prosodyctl --- a/prosodyctl Wed Jul 24 10:37:01 2019 -0700 +++ b/prosodyctl Wed Jul 24 10:43:28 2019 -0700 @@ -90,6 +90,12 @@ show_usage([[make]], [[Installs a prosody/luarocks plugin]]); return 1; end + local installer_plugin_path + -- I'm considering that we are using just one path to custom plugins, and it is the first in prosody.paths.plugins, for now + for path in prosody.paths.plugins:gmatch("[^;]+") do + installer_plugin_path = path + break + end -- I'm considering this optional flag comes first local flag = "--tree=" if arg[1] and arg[1]:sub(1, #flag) == flag then @@ -99,10 +105,10 @@ show_module_configuration_help(arg[2]); return 0; else - print("Installing module "..arg[1].." at "..prosody.paths.plugins) + print("Installing module "..arg[1].." at "..installer_plugin_path) -- I've build a local server to upload some new rockspecs, like mod_smacks'. We can replace this server by one from -- prosody's, where we can oficially disbrute rocks/rockspecs for all modules - os.execute("luarocks --tree='"..prosody.paths.plugins.."' --server='http://localhost/' install "..arg[1]) + os.execute("luarocks --tree='"..installer_plugin_path.."' --server='http://localhost/' install "..arg[1]) show_module_configuration_help(arg[1]); return 0; end