From 275b31b0cf7c91a549a996b9c714def5bac5c4a4 Mon Sep 17 00:00:00 2001 From: Alexey Shchepin Date: Tue, 28 Jan 2003 19:45:13 +0000 Subject: *** empty log message *** SVN Revision: 52 --- doc/guide.html | 19 ++++++++++++++++--- 1 file changed, 16 insertions(+), 3 deletions(-) (limited to 'doc/guide.html') diff --git a/doc/guide.html b/doc/guide.html index 7356258c..bb18b0ea 100644 --- a/doc/guide.html +++ b/doc/guide.html @@ -72,7 +72,20 @@ Latest alpha version can be retrieved via CVS. Do following steps:

2.3   Compilation

- +
+./configure
+make
+
TBD
+
+ + +

2.4   Starting

+ +
+erl -name ejabberd -s ejabberd
+
TBD
+
+

3   Configuration

@@ -216,12 +229,12 @@ TBD

4.1   How it works

Jabber domain is served by one or more ejabberd nodes. This nodes can be -runned on different computers that can be connected via network. They all must +runned on different machines that can be connected via network. They all must have access to connect to port 4369 of all another nodes, and must have same magic cookie (see Erlang/OTP documentation, in short file ejabberd/.erlang.cookie must be the same on all nodes). This is needed because all nodes exchange information about connected users, S2S -connection ,registered services, etc...
+connection, registered services, etc...

Each ejabberd node run following modules: