74 lines
2.1 KiB
Plaintext
74 lines
2.1 KiB
Plaintext
|
Release notes
|
||
|
ejabberd 0.9
|
||
|
|
||
|
This document describes the major new features of and changes to
|
||
|
ejabberd 0.9, compared to latest public release ejabber 0.7.5.
|
||
|
|
||
|
For more detailed information, please refer to ejabberd User
|
||
|
Guide.
|
||
|
|
||
|
|
||
|
Virtual Hosting
|
||
|
|
||
|
ejabberd now can host several domain on the same instance.
|
||
|
This option is enabled by using:
|
||
|
|
||
|
{hosts, ["erlang-projects.org", "erlang-fr.org"]}.
|
||
|
|
||
|
instead of the previous host directive.
|
||
|
|
||
|
Note that you are now using a list of hosts. The main one should
|
||
|
be the first listed. See migration note further for details.
|
||
|
|
||
|
|
||
|
Shared Roster
|
||
|
|
||
|
Shared roster is a new feature that allow the ejabberd
|
||
|
administrator to add jabber user that will be present in the
|
||
|
roster of every users on the server.
|
||
|
Shared roster are enabled by adding:
|
||
|
|
||
|
{mod_shared_roster, []}
|
||
|
|
||
|
at the end of your module list in your ejabberd.cfg file.
|
||
|
|
||
|
|
||
|
PostgreSQL (ODBC) support
|
||
|
|
||
|
PostgreSQL support is enabled by using the following module in
|
||
|
ejabberd.cfg instead of their standard counterpart:
|
||
|
|
||
|
mod_last_odbc.erl
|
||
|
mod_offline_odbc.erl
|
||
|
mod_roster_odbc.erl
|
||
|
|
||
|
The database schema is located in the src/odbc/pq.sql file.
|
||
|
|
||
|
|
||
|
Migration from ejabberd 0.7.5
|
||
|
|
||
|
Migration is pretty straightforward as Mnesia database schema
|
||
|
converions is handled automatically.
|
||
|
Here are the following steps to proceed:
|
||
|
|
||
|
1. Stop your instance of ejabberd.
|
||
|
|
||
|
2. In ejabberd.cfg, define the host lists. Change the host
|
||
|
directive to the hosts one:
|
||
|
Before:
|
||
|
{host, "erlang-projects.org"}.
|
||
|
After:
|
||
|
{hosts, ["erlang-projects.org", "erlang-fr.org"]}.
|
||
|
Note that when you restart the server the existing users will be
|
||
|
affected to the first virtual host, so the order is important. You
|
||
|
should keep the previous hostname as the first virtual host.
|
||
|
|
||
|
3. Restart ejabberd.
|
||
|
|
||
|
|
||
|
Bugfixes
|
||
|
|
||
|
This release contains several bugfixes and architectural changes.
|
||
|
Please refer to the Changelog file supplied with this release for
|
||
|
details of all improvements in the ejabberd code.
|