Avançar para o conteúdo principal

Sailing!

After some fusion dance, we have some stuff working neatly! Last week was all about the lua environment and improvements aimed at user-friendliness, which you can check down below with latest changesets and demos.

Events

prosodyctl

  • Removed most development/experimental commands
  • Created a script that is automatically setting up a ready to be served repository will rockspecs for all of prosody's plugins (demo)
  • Various improvements/updates to the main commands:
  • prosody uses a separate folder to deal with non-standard plugins - demo
  • Users can configure their own path, and override it at any time from the command line if needed - demo
  • Updated the startup utility script regarding management of default/custom installer directories and lua environment

Difficulties

The greatest obstacles this past week were everything related with the concept of lua environment and its setup, which I wasn't really familiar with. Right now I *think* I have a clearer idea of what I'm doing when messing with that, after some explanations and research. Prosody is now complementing a its process's Lua environment with the required paths.
For people who are new to the concept like me, this is a cool source of info that I've found and you might want to check out.

Future goals

Code right now is a bit too messy after all the turmoil to get things working, and that needs to be improved this week.
There are also some minor issues left regarding rockspecs and pathing that I need to check to make sure are right. Specifically, I'm still having some trouble with modules that have more than one file or more complex structures, and making sure prosody is really finding everything it needs regarding installed plugins and lua libraries, although so far it seems to be okay.
Some first serious steps into documentation should also be made until the next blog. Time is flying, and its August right around the corner. This is GSoC's last month =[

Comentários

Enviar um comentário

Mensagens populares deste blogue

Prosody's plugin installer is making use of Luarocks to get things working. Therefore, it makes sense that we look a bit into Luarocks to see how it works. Concepts Here is what you need to know. Luarocks uses files, called rockspecs, to get things installed around. These are basically instruction files and they tell the program how to do the work. We can pack the sources and the rockspecs into a single file, called a rock. We can install libraries from both rocks and rockspec files. The code is installed in what is called a rock tree, which is a folder with a specific structure inside, organized in a way to help with the required management of libraries and servers. Installing, removing and list If you are working on debian you can just use: sudo apt-get install luarocks Now, there might be some trouble here and there, depending on your machine, or if you are in a different OS, but the guys at luarocks have tips for almost every possible situation, just che...
Enviar um comentário
Ler mais
Prosody's plugin installer is making use of Luarocks to work underneath the hood. Therefore, it makes sense that we look a bit into Luarocks to see how it works. Concepts Here is what you need to know. From the perspective of Luarocks, Lua Libraries are files called Rocks. Rock files are like a zip file, in the sense that inside there are many files. Most of those files are the sources, which means those are the files that have all the code itself. And then there is a rockspec file. This is like an instruction file, written in Lua, which contains the important information that Luarocks needs to do its job. Things like the location of sources, dependencies and build instructions. The code is then installed in what is called a rock tree. A normal folder, in other words. But this folder is referenced on luarocks documentation, for example, so that things know where to look for when they need to use a particular library. Installing, removing as list If you ...
Enviar um comentário
Ler mais