jacob.eva
/
ejabberd-contrib
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
Growing and curated ejabberd contributions repository - PR or ask to join !
185 Commits 3 Branches 0 Tags 8.3 MiB
Erlang 98.7%
Ruby 0.9%
Elixir 0.2%
TSQL 0.2%
Go to file
Holger Weiss e0557b9e26 Advertise feature in disco info for account JID 
As per XEP-0313 >= 0.2, advertise the MAM feature in the service
discovery information for the bare account JID.

Some clients check the server's discovery information instead, so we'll
continue to advertise the feature there as well (at least for the
moment).
 		2015-04-26 17:17:21 +02:00
atom_pubsub Document the five contributions that don't work with ejabberd 13 or newer 2015-02-06 12:54:49 +01:00
ejabberd-dev Update jlib header from ejabberd master 2015-03-21 20:49:04 +01:00
ejabberd_auth_http Update README files to show configuration file as YAML (#86) 2015-03-13 11:55:26 +01:00
ircd Document the five contributions that don't work with ejabberd 13 or newer 2015-02-06 12:54:49 +01:00
mod_admin_extra Update README files to show configuration file as YAML (#86) 2015-03-13 11:55:26 +01:00
mod_archive Document the five contributions that don't work with ejabberd 13 or newer 2015-02-06 12:54:49 +01:00
mod_cron Update README files to show configuration file as YAML (#86) 2015-03-13 11:55:26 +01:00
mod_log_chat Update FSF address (solves #73) 2015-02-25 15:17:31 +01:00
mod_logsession Update README files to show configuration file as YAML (#86) 2015-03-13 11:55:26 +01:00
mod_logxml Update FSF address (solves #73) 2015-02-25 15:17:31 +01:00
mod_mam Advertise feature in disco info for account JID 2015-04-26 17:17:21 +02:00
mod_message_log Update README files to show configuration file as YAML (#86) 2015-03-13 11:55:26 +01:00
mod_muc_admin Update README files to show configuration file as YAML (#86) 2015-03-13 11:55:26 +01:00
mod_muc_log_http Update README files to show configuration file as YAML (#86) 2015-03-13 11:55:26 +01:00
mod_multicast Update README files to show configuration file as YAML (#86) 2015-03-13 11:55:26 +01:00
mod_openid Document the five contributions that don't work with ejabberd 13 or newer 2015-02-06 12:54:49 +01:00
mod_post_log Add README and license to mod_post_log 2015-02-25 15:43:22 -03:00
mod_profile binarize mod_profile 2015-03-13 11:13:40 +01:00
mod_rest Update README files to show configuration file as YAML (#86) 2015-03-13 11:55:26 +01:00
mod_s2s_log Update README files to show configuration file as YAML (#86) 2015-03-13 11:55:26 +01:00
mod_shcommands Update README files to show configuration file as YAML (#86) 2015-03-13 11:55:26 +01:00
mod_statsdx Update README files to show configuration file as YAML (#86) 2015-03-13 11:55:26 +01:00
mod_webpresence Update README files to show configuration file as YAML (#86) 2015-03-13 11:55:26 +01:00
.gitignore Ignore .beam files 2014-03-14 11:47:54 -05:00
README-broken.md Add list of broken module 2015-02-11 16:21:43 +01:00
README.md Convert README to Markdown 2014-05-27 21:22:42 +02:00
extract-mod-translations.sh Initial import from ejabberd-modules SVN 2013-04-15 12:03:14 +02:00

README.md

ejabberd-contrib

This is a collaborative development area for ejabberd module developers and users.

For users

To use an ejabberd module coming from this repository:

  • You need to have Erlang installed.

  • Read the module-specific README.txt file to see if special steps are required to deploy it.

  • Run ./build.sh or build.bat in the root directory of the desired module.

  • Copy generated .beam files from the ebin directory to the directory where your ejabberd .beam files are.

  • Use the configuration file examples provided in the conf dir to update your ejabberd.cfg or ejabberd.yml configuration file.

If during compilation of a module you get an error like:

{"init terminating in do_boot",{undef,[{make,all,[]},...

it means Erlang couldn't find its make.beam file. In Debian and other distributions you can try to install packages like:

erlang-dev erlang-nox erlang-tools

For developers

The following organization has been set up for the development:

  • Development and compilation of modules should be possible without the ejabberd source code, as the ejabberd-dev helper module contains the include files necessary to make compilation possible.

  • The module directory structure is usually the following:

    • README.txt: Module description.
    • LICENSE.txt: License for the module.
    • Emakefile: Erlang Makefile to build the module (preferred way, if no dependencies on C code, as build will thus work on Windows).
    • doc/: Documentation directory.
    • src/: Source directory.
    • src/msgs/: Directory with translation files (pot, po and msg).
    • ebin/: Empty (target directory for the build).
    • conf/: Directory containing example configuration for your module.
    • build.sh: Unix/Linux build script.
    • build.bat: Windows build script.

  • Module developers should note in the README.txt file whether the module has requirements or known incompatibilities with other modules (for example, by modifying the same main ejabberd modules).