Here we are. This post is the conclusion of the official GSoC journey with prosody! Check out below what this project is, what it is currently doing and how things can keep on going! First of all, where is the stuff? The code is right here ! This is everything that made it to the trunk merge. If you want to see the installer in action and how to use it, you can check this demonstration .  If you want instead to see all of the changesets I've made throughout the months, you can check them here . Finally, here you have the project's link in case you want to check it out! Really briefly, what was this all about again? ProsodyIM is a XMPP server. People can set it up with a lot of different functionalities. These are provided by what the community calls modules or plugins. Prosody only comes with a given set of core modules but there are many others that we can use. We aimed at providing an easy way to install those, because previously, the user had to go to a mercu...

Nearly out of time! Some final adjustments were made this week, documentation was accordingly updated and preparations are being made to the deliver GSoC's official final submission. Check out the latest changes in this week's blogpost! Events Code 1 - prosodyctl: fixed a typo 2 - util.startup: changed the way util.paths.complement_lua_path was being accessed 3 - util.paths: fixed another typo 4 - util.pluginloader: Added a new path to the variable local_names 5 - core.configmanager: Removed code related to complement_lua_path 6 - prosodyctl: install, remove and list commands now use the call_luarocks function 7 - util.prosodyctl: Removed the check_flags and execute_command functions 8 - util.prosodyctl: call_luarocks function now sets the directory variable itself Documentation These are planned changes to the already existing documentation that you can access at prosody's website. For example, you can check prosodyctl's page through the lin...

Last week has been spent mostly on writing good documentation and trying to see what else can be improved around whats done. Check out below, to see which doc files are about to be updated so far! Prosody documentation: /doc/prosodyctl- added command entries /doc/prosodyctl - Added a reference to the plugin installer documentation page /doc - Added a reference to the plugin installer documentation page /doc/plugin_installer - Created this new page /doc/plugin_installer - Added introduction, pointing to links regarding prosodyctl, core and community modules, installing modules manually /doc/example_config - Added the new field for the plugin installer directory /doc/configure - Added info about configuring the installer's path Difficulties/Considerations Not too sure what to do with /doc/installing_modules. I could update the installer info here, but I feel it needs a dedicated space. This space is still useful on its own, since core plugins are still coming ins...

Code review was in order last week, and some major improvements were made regarding my pseudo-spaghetti code, which now should be more readable and maintainable. Down below you can check out the complete list of changes made recently to prosody files, in order to polish the Installer! Events prosodyctl 1 : Swapped prints for the show_message function 2 : Removed a comment from the remove command 3 : Rewrote the install command 4 : Rewrote the remove command 5 : Rewrote the list command, to make it cleaner and easier to work with 6 : Install, remove and list now use the execute_command instead 7 : Removed the auxiliary command enabled_plugins core/configmanager 1 : Added support to complement_lua_path util//prosodyctl 1 : Added the check_flags function - changeset 2 : Added the call_luarocks function 3 : call_luarocks command differentiates output, when being called by install/remove 4 : The call_luarocks function can now also deal with the list command 5 :...