Ejabberd Community 13.10 supports YAML format for configuration file. Ejabberd newcomers were often frighten editing Erlang term file (ejabberd.cfg) and the YAML support is a way to help configuring ejabberd using a more familiar text format. It’s possible to convert ejabberd configuration to YAML using convert_to_yaml command from ejabberdctl.
After installing ejabberd 13.10 from binary installer, which comes by default with Erlang terms based configuration, just create your YAML configuration this way:
bin/ejabberdctl convert_to_yaml $PWD/conf/ejabberd.cfg $PWD/conf/ejabberd.yml
You can check/edit your new configuration. Default configuration looks like this:
body: "Welcome to this Jabber server."
How to let ejabberd use the YAML configuration file?
If you installed ejabberd from binary installer, you must edit ejabberdctl script to change configuration file extension on the EJABBERD_CONFIG_PATH environment variable, at line 95.
If you installed ejabberd from sources or any other packaging system, ejabberdctl should already be configured to use YAML file, with following environment definition
Then, just restart ejabberd.
Et voilà !
We are pleased to announce a new stable release of ejabberd, ejabberd Community 13.10.
It has some changes, several improvements and many bugfixes over the previous (not officially announced) 13.06. It is also the first official stable release of ejabberd Community after ejabberd 2.1.13. You are now pleased to use ejabberd community as reference for stable releases of ejabberd, from the master branch. ejabberd 2.1.x support is discontinued.
The most noticeable changes since 13.03-beta and 13.06 are:
- in the configuration file: it is now written using YAML syntax instead of Erlang syntax. So, after installing ejabberd, search for a file called ejabberd.yml. If you have an old ejabberd.cfg, you can convert it to yml using the “ejabberdctl convert_to_yaml” command. The ejabberd Guide is fully updated to describe the new syntax.
- in logging system: it now uses Lager to produce cleaner logs, with a “one line per element” scheme.
- in build process: now Rebar is used for simpler dependency handling, so code is modular among several repositories, putting out of ejabberd general purpose libraries.
Changes since 2.1.13 are even more noticeable:
- huge improvements regarding performances
- optimized memory consumption
- clean code representation of xmlel records
As usual, the release is tagged in the Git source code repository on github
The source package and binary installers are available at ProcessOne
If you suspect you found a bug, search or fill a bug report in Jira
Please note this branch requires at least Erlang/OTP R15, and works correctly with R16B02.
Here at ProcessOne we are in the business of building and managing huge scale robust platforms. For our relaunch of the Boxcar platforms for mobile developers, we are sending notifications to mobile users on behalf of our customers. Millions of them. Be it APNS or GCM, the timely deliver of every one of them is our core task, and we need to be sure that all our infrastructure is ready for it.
One of the key components of our system is written in Erlang, where we use the well-know emysql library for accessing our DB. One of the problems we first hit, is that the performance of emysql is far from optimal when the result set contains a large number of rows. We found it to be really slow for these cases.
ProcessOne is in the business of building and running huge real-time projects for our customers. It is often a cause of frustration when comes the time to explain what you are doing publicly. As we are working on large scale mission critical projects, this often means that we have agreed to keep our work strictly confidential.
We have been building a large scale, robust, and cost effective platform for sending iOS and Android push notifications since many years now. However, very few people are aware of the fact that we have in our hand one of the fastest (if not the fastest) push notification services in the world. And we think it compare favourably to competitors like Parse and Urban Airship.
However, until now, it was a very well kept secret. Boxcar relaunch announce is our way to take our opportunity to spread the word by making that platform available not only to large brands, but to all mobile developers.
As you know, ProcessOne is about realtime messaging. Our core component is XMPP ejabberd scalable and ubiquitous server. We recently acquired Boxcar to use a familiar and popular brand for our large scale push notification service for mobile as well.
From this perspective, Google’s huge update on its Cloud Messaging service is the biggest announcement from this year Google I/O, as it mixes our two core strengths. We strongly believe this is a big deal for mobile developers and we will explain why.
Today was the keynote of Google I/O developer conference. The keynote is usually the place where major announcements are made regarding the Google ecosystem.
Despite impressive announcements, the most important thing that strikes me is not what has been released, but what has not been mentioned.
If you are a student excited by XMPP, high-performance and Erlang, this should be great news.
We are announcing two major changes in ejabberd development today:
- a new version of ejabberd, called ejabberd Community Server (eCS), as opposed to ejabberd Business Edition (eBE)
- a change in version numbering, and thus our workflow
As founder of ProcessOne, I’ve promoted since 10 years a vision made of real-time messages exchanged at an Internet scale. Together with ProcessOne team, we stayed true to that vision using the best technologies to make that ambition happen. Erlang is a dream environment to build fast and scalable real-time system. XMPP (eXtensible Messaging and Presence Protocol) is a protocol of choice to make people communicate over a federation of servers and a de facto standard today.
What we did is that we combined those two technologies to build the de facto standard component available to build Instant Messaging, Group Messaging, Social Messaging on a large scale. The software we have built is deployed on the largest chat deployments across the world. We have seen ejabberd in tens of thousands of deployments. We have seen ejabberd being adopted by large, renowed brands. We have invented protocols and extensions to push the messaging system further. We have traveled around the world to get those companies get the best of the tools we produced.
ProcessOne is entering in an agreement with Kwaga to acquire Boxcar world-class push notification service as well as all technologies, intellectual property and trademark from Kwaga, the editor of WriteThatName.