Ejabberd 2.0.5 install#
Ejabberd 2.0.5 update#
Ejabberd 2.0.5 code#
Ejabberd 2.0.5 download#

Next step - configure external XMPP component on ejabberd side.

This is an important change, especially if you're planning to reuse your EC2 instance I will omit the explanation for now. Once installation is completed, edit ejabberdctl.cfg by changing the very last line zephyr.local Note default installation directory ( /opt/ejabberd-2.0.5 by default), you will need it shortly. Make default choices during installation when asked about ejabberd server domain, enter host name you previously added to /etc/hosts (i.e. Gunzip ejabberd-2.0.Ĭhmod 755 ejabberd-2.0.5-linux-x86-installer.bin Note: You will be using this domain name in many places, so please make note of it I will be using zephyr.local in this post going forward.ĭownload, unpack and launch ejabberd installer: The first line in /etc/hosts after editing will look something like (substitute zephyr to anything you like):ġ27.0.0.1 localhost.localdomain localhost zephyr.local We need to add a Jabber domain name to /etc/hosts first. Then everything went fine and you can type q().

Ejabberd 2.0.5 download#

Now, download the exmpp distribution and build:Īt this point you may want to check if exmpp is in working condition.

Ejabberd 2.0.5 install#

Update: the demo will work fine with libxml2, however, at the time of writing (Nov 07, 2009), if you're planning to use exmpp for other purposes, particularly, exmpp_session module, you're advised to install libexpat1-dev instead. First, we need to install some libraries that exmpp is using for XML support: Then install Erlang (version R12B5 or newer karmic has R13B01): We'll need svn to checkout some stuff later:

Ejabberd 2.0.5 update#

Sudo apt-get update & sudo apt-get upgrade So, provided you have running instance of ami-19a34270, let's ssh to it and start by: Major components to install and configure are: In conclusion, check out much more comprehensive discussion of typing problem in Erlang.īrace yourself, that's going to be a long one. To me, having to have function specs in the code, while being a good thing on its own, is a very small price for the feeling of liberation and increased performance that dynamic typing in Erlang gives you compared to a static one in Java.

Ejabberd 2.0.5 code#

By the way, exmpp team really impressed me by thoroughly following this path throughout entire code base. I'm now ready to make resolution to have specifications for every single function in my code, including non-API functions. Having function specifications will hugely help anyone who will ever have to work with the code, including the owner. It could have been much easier, though, if the code was accompanied by documentation markup.

This, of course, is an intrusive action and assumes the source code is available. So, after few attempts trying to mentally trace some of mnesia transactions, I suddenly felt my brain overloaded and had to resort to debugging ejabberd from remote node :-) I had to recompile the module with -compile(export_all) in order to be able to try functions that contained mnesia code in Erlang shell and figure out their exact output. Java methods, on the other hand, always have statically typed output, which obviously eliminates any guessing work. It might sound like fairly routine task, and it was for the most part, except sometimes it's hard to reason about Erlang function output just by looking at the source code. Or maybe you will occasionally, like I did few days back, when I was charged with the task of cloning ejabberd module by replacing mnesia with odbc calls. Peace and let's say no to flame wars, comrades! Don't get me wrong, Java is an awesome language, but if you have already started serious coding in Erlang, you will probably never look back.