Installation using the *.run binary installer:ĭownload the run package for your architecture Is the release number, for example 18.01. In this document, when mentioning ejabberd-YY.MM, we assume YY.MM Those instructions assume installation on localhost for development purposes.
Ejabberd 2 install#
As such, when usingĮjabberd installer, you do not need to install Erlang separately. Includes a stripped down version of Erlang.
Ejabberd 2 full#
The *.run binary installer will deploy and configure a full featuredĮjabberd server and does not require any extra dependencies. Once installed, you can head to the next steps:
Source Code – for developers and advanced administrators.Docker Image – for Windows, macOS, Linux.Operating System packages – for System Operators.Linux DEB and RPM Installers – for DEB and RPM based Linux.All comments refer to ejabbered 2.0.There are several ways to install ejabberd Community Server: without Psi XML console it would have been impossible to figure this all out - Psi rocks ! (first attempts to create a named node get error auth 403 forbidden) and the weirdest behaviour is that each user has to createĪn instant node before they can create a named node !?!? Underneath, and the type switches to collection !Įjabbered advertises feature pubsub#delete-nodes and it should be supported,īecause it does support pubsub#create-nodes (XEP-0060 Section 8.4) ,īut any attempt to delete a node returns error 501 cancel feature-not-implemented. Have pubsub#node_type leaf, but then you can add nodes when ejabberd is installed, the /home/myhost and /pubsub/nodes pubsub#node_type appears to be mutable !?Į.g.(in fact, you must not include pubsub#collection in create,īecause it is error modify 406 not-acceptable) home/myhost/username without having to add this to the config home/myhost/username/foo implies pubsub#collection property Two other interesting points that don't exactly leap out of the spec:Ī structured name implies the parent collection as a tree: How can I find out the owner of a node under /pubsub/nodes ? How can nodes be added under /pubsub/nodes ? So if any user can only create nodes under /home/myhost/username, (this is the response, because I am subscribed to the node) Brief description of some mod_pubsub plugins.How much of XEP-0060 is implemented in ejabberd 2.0.2.Or to take arms against a sea of troubles, The slings and arrows of outrageous fortune, Whether 'tis nobler in the mind to suffer To be, or not to be: that is the question: Then he publishes an item with an ItemID: The account creates his first node:Įxample for 2.1.0 with plugin "flat". create an instant node), the server generates a name that fits this pattern.Įxample for 2.0.5 with plugin "default". If you try to create a node whose name doesn't fit that pattern, you will get an error. Nodes of users have names like home/ server/ username/ whatever. There is a special node, pubsub/nodes, that contains all other created nodes. mod_pubsub imposes a special structure on this tree. Pubsub nodes are organized in a hierarchical tree, similar to a file system. It is also supposed that you have a Jabber client that supports Pubsub (as opposed to PEP), or are prepared to craft and send the stanzas by hand.
Ejabberd 2 how to#
It does not describe how to use PEP (XEP-0163).
This page describes how to use ejabberd's mod_pubsub, an implementation of XEP-0060.
0 kommentar(er)
