25
1
mirror of https://github.com/processone/ejabberd.git synced 2024-12-22 17:28:25 +01:00
Go to file
Badlop 937e1c2e37 Add workaround so rebar2 can use Elixir 1.12.0
Notice that Elixir 1.12.0 requires Erlang/OTP 21 or higher
BTW, this workaround works only with rebar2... unfortunately
rebar3 doesn't compile the elixir files from lib/
2021-07-16 16:43:08 +02:00
_checkouts/configure_deps Improve rebar3 configure-deps plugin output 2020-09-23 17:56:49 +01:00
.devcontainer Use the new Github container registry 2021-05-12 11:51:40 +02:00
.github Add support for rebar3 to "make rel" 2021-06-25 12:53:22 +02:00
config As Mix config now must be evaluated at runtime, rename to runtime.exs 2021-07-16 13:57:25 +02:00
examples Remove old and obsolete examples/transport-configs/ (#3487) 2021-01-27 17:10:56 +01:00
include New 'note' field in commands and options documentation 2021-05-05 11:57:02 +02:00
lib Add workaround so rebar2 can use Elixir 1.12.0 2021-07-16 16:43:08 +02:00
m4 Do not check for deprecated types 2018-06-14 18:58:35 +03:00
man Recompile man page with "ejabberdctl man" 2021-03-26 11:05:49 +01:00
plugins Rename plugin to not clash with plugin from dep 2020-01-08 10:41:48 +01:00
priv New Albanian translation (thanks to Besnik Bleta) 2021-04-07 16:01:28 +02:00
rel Update setup-dev.sh to work perfectly both with rebar3 and mix 2021-07-16 13:36:22 +02:00
sql Add mqtt_pub table definition for MSSQL (#3097) 2021-06-14 12:22:21 +02:00
src erlang:phash is deprecated in OTP 24, let's use phash2 2021-07-16 13:57:08 +02:00
test Fix extauth.py failure in test suite with Python 3 (#3612) 2021-05-25 18:39:18 +02:00
tools Support the recent changes in the "ejabberdctl help" command (#3569) 2021-04-15 20:25:54 +02:00
.dockerignore add docker support 2016-11-16 11:48:50 +01:00
.gitignore Add support to build release with back to old Elixir 1.10.3 2021-07-16 13:36:27 +02:00
autogen.sh Force regeneration of configure script 2014-04-18 12:13:17 +02:00
CHANGELOG.md Update changelog 2020-12-15 15:26:23 +01:00
CODE_OF_CONDUCT.md Create CODE_OF_CONDUCT.md 2018-01-09 14:17:55 +01:00
configure.ac Add support for mix to: ./configure --enable-rebar=mix 2021-07-16 13:36:23 +02:00
configure.bat Switch to rebar build tool 2013-06-13 11:11:02 +02:00
CONTRIBUTING.md Remove .travis.yml as it's superseded by ci.yml (#3613) 2021-05-25 19:16:06 +02:00
CONTRIBUTORS.md CONTRIBUTORS: UTF-8 encode my name 2018-11-19 15:23:35 +01:00
COPYING Update FSF address 2014-02-22 10:27:40 +00:00
cover.spec Add Coveralls support 2016-03-21 12:01:20 +01:00
ejabberd.init.template Replace Jabber->XMPP and Ejabberd (thanks to Neustradamus)(#3469) 2021-01-11 21:11:20 +01:00
ejabberd.service.template Allow for listening on privileged ports 2021-01-06 18:56:08 +01:00
ejabberd.yml.example New listener for encrypted ejabberd_c2s 2021-02-02 15:25:19 +01:00
ejabberdctl.cfg.example Remove SMP option from ejabberdctl.cfg, -smp was removed in OTP 21 (#3560) 2021-04-15 20:28:43 +02:00
ejabberdctl.template Set SCRIPT_DIR as done by the ejabberd script generated by "rebar3 release" 2021-06-25 12:53:30 +02:00
inetrc Switch to rebar build tool 2013-06-13 11:11:02 +02:00
install-sh Switch to rebar build tool 2013-06-13 11:11:02 +02:00
Makefile.in Add workaround so rebar2 can use Elixir 1.12.0 2021-07-16 16:43:08 +02:00
mix.exs Add support to build release with back to old Elixir 1.10.3 2021-07-16 13:36:27 +02:00
mix.lock Update stringprep in mix 2021-06-18 11:45:18 +02:00
README.md Mention in README.md the updated --with-rebar and "make dev" 2021-07-16 13:36:28 +02:00
rebar Recompile rebar script with OTP17.5 2017-08-23 11:45:10 +03:00
rebar3 Add rebar3 3.15.2 2021-07-16 13:36:25 +02:00
rebar.config Add workaround so rebar2 can use Elixir 1.12.0 2021-07-16 16:43:08 +02:00
rebar.config.script Include odbc app in release only when required (#3633) 2021-06-27 17:32:09 +02:00
vars.config.in Generate enabled_backends in ejabberd.app instead of configure (#3549) 2021-03-15 10:11:05 +01:00

ejabberd Community Edition

CI Coverage Status Translation status Hex version

ejabberd is a distributed, fault-tolerant technology that allows the creation of large-scale instant messaging applications. The server can reliably support thousands of simultaneous users on a single node and has been designed to provide exceptional standards of fault tolerance. As an open source technology, based on industry-standards, ejabberd can be used to build bespoke solutions very cost effectively.

Key Features

  • Cross-platform
    ejabberd runs under Microsoft Windows and Unix-derived systems such as Linux, FreeBSD and NetBSD.

  • Distributed
    You can run ejabberd on a cluster of machines and all of them will serve the same XMPP domain(s). When you need more capacity you can simply add a new cheap node to your cluster. Accordingly, you do not need to buy an expensive high-end machine to support tens of thousands concurrent users.

  • Fault-tolerant
    You can deploy an ejabberd cluster so that all the information required for a properly working service will be replicated permanently on all nodes. This means that if one of the nodes crashes, the others will continue working without disruption. In addition, nodes also can be added or replaced on the fly.

  • Administrator-friendly
    ejabberd is built on top of the Open Source Erlang. As a result you do not need to install an external database, an external web server, amongst others because everything is already included, and ready to run out of the box. Other administrator benefits include:

    • Comprehensive documentation.
    • Straightforward installers for Linux.
    • Docker packaging to help with deploy / development on Linux, Windows or MacOS.
    • Deb and RPM packaging to support most Linux distributions.
    • Web administration.
    • Shared roster groups.
    • Command line administration tool.
    • Can integrate with existing authentication mechanisms.
    • Capability to send announce messages.
  • Internationalized
    ejabberd leads in internationalization. Hence it is very well suited in a globalized world. Related features are:

    • Translated to 25 languages.
    • Support for IDNA.
  • Open Standards
    ejabberd is the first Open Source XMPP server claiming to fully comply to the XMPP standard.

    • Fully XMPP-compliant.
    • XML-based protocol.
    • Many protocols supported.

Additional Features

Moreover, ejabberd comes with a wide range of other state-of-the-art features:

  • Modularity

    • Load only the modules you want.
    • Extend ejabberd with your own custom modules.
  • Security

    • SASL and STARTTLS for c2s and s2s connections.
    • STARTTLS and Dialback s2s connections.
    • Web Admin accessible via HTTPS secure access.
  • Databases

    • Internal database for fast deployment (Mnesia).
    • Native MySQL support.
    • Native PostgreSQL support.
    • ODBC data storage support.
    • Microsoft SQL Server support.
  • Authentication

    • Internal authentication.
    • PAM, LDAP and ODBC.
    • External authentication script.
  • Others

    • Support for virtual hosting.
    • Compressing XML streams with Stream Compression (XEP-0138).
    • Statistics via Statistics Gathering (XEP-0039).
    • IPv6 support both for c2s and s2s connections.
    • Multi-User Chat module with support for clustering and HTML logging.
    • Users Directory based on users vCards.
    • Publish-Subscribe component with support for Personal Eventing.
    • Support for web clients: HTTP Polling and HTTP Binding (BOSH).
    • Component support: interface with networks such as AIM, ICQ and MSN.

Quickstart guide

0. Requirements

To compile ejabberd you need:

  • GNU Make.
  • GCC.
  • Libexpat ≥ 1.95.
  • Libyaml ≥ 0.1.4.
  • Erlang/OTP ≥ 19.3.
  • OpenSSL ≥ 1.0.0.
  • Zlib ≥ 1.2.3, for Stream Compression support (XEP-0138). Optional.
  • PAM library. Optional. For Pluggable Authentication Modules (PAM).
  • ImageMagick's Convert program and Ghostscript fonts. Optional. For CAPTCHA challenges.
  • Elixir ≥ 1.10.3. Optional. Alternative to build ejabberd

If your system splits packages in libraries and development headers, you must install the development packages also.

1. Compile and install on *nix systems

To compile ejabberd, execute the following commands. The first one is only necessary if your source tree didn't come with a configure script (In this case you need autoconf installed).

./autogen.sh
./configure
make

To install ejabberd, run this command with system administrator rights (root user):

sudo make install

These commands will:

  • Install the configuration files in /etc/ejabberd/
  • Install ejabberd binary, header and runtime files in /lib/ejabberd/
  • Install the administration script: /sbin/ejabberdctl
  • Install ejabberd documentation in /share/doc/ejabberd/
  • Create a spool directory: /var/lib/ejabberd/
  • Create a directory for log files: /var/log/ejabberd/

2. Start ejabberd

You can use the ejabberdctl command line administration script to start and stop ejabberd. For example:

ejabberdctl start

For detailed information please refer to the ejabberd Documentation

3. Use ejabberd locally

Alternatively, you can setup ejabberd without installing in your system:

./configure --with-rebar=./rebar3
make dev

Or, if you have Elixir available and plan to develop Elixir code:

./configure --with-rebar=mix
make dev

Check the full list of targets:

make help

Development

In order to assist in the development of ejabberd, and particularly the execution of the test suite, a Vagrant environment is available at https://github.com/processone/ejabberd-vagrant-dev.

To start ejabberd in development mode from the repository directory, you can type a command like:

EJABBERD_CONFIG_PATH=ejabberd.yml erl -pa ebin -pa deps/*/ebin -pa test -pa deps/elixir/lib/*/ebin/ -s ejabberd

Translation

Using any gettext editor, you can improve the translation files found in priv/msgs/*.po, and then submit your changes.

Alternatively, a simple way to improve translations is using our Weblate project: https://hosted.weblate.org/projects/ejabberd/ejabberd-po/