diff --git a/README.md b/README.md index 0f0063d0ff..86f7fa3595 100644 --- a/README.md +++ b/README.md @@ -70,37 +70,37 @@ How to build $ ./rebar generate These commands will generate a self-contained OTP system image in the - project's `rel/ejabberd` subdirectory. The contents of that directory are as + project's `rel/mongooseim` subdirectory. The contents of that directory are as follows: - * `rel/ejabberd/bin` - startup/administration scripts, - * `rel/ejabberd/etc` - configuration files, - * `rel/ejabberd/lib` - MongooseIM binary, header and runtime files, - * `rel/ejabberd/var` - spool directory, - * `rel/ejabberd/log` - log file directory, - * `rel/ejabberd/releases` - release files directory. + * `rel/mongooseim/bin` - startup/administration scripts, + * `rel/mongooseim/etc` - configuration files, + * `rel/mongooseim/lib` - MongooseIM binary, header and runtime files, + * `rel/mongooseim/var` - spool directory, + * `rel/mongooseim/log` - log file directory, + * `rel/mongooseim/releases` - release files directory. 3. Running MongooseIM. To run MongooseIM from the project tree after compiling it, change - to `$REPO/rel/ejabberd`. + to `$REPO/rel/mongooseim`. - There you can use the `ejabberd` command line administration script to - start and stop ejabberd. For example: + There you can use the `mongooseim` command line administration script to + start and stop MongooseIM. For example: - $ bin/ejabberd start + $ bin/mongooseim start will start the server. You can also run the server in interactive mode: - $ bin/ejabberd live + $ bin/mongooseim live - There's also a tool called `ejabberdctl` allowing you to perform some + There's also a tool called `mongooseimctl` allowing you to perform some operations on a running instance, e.g.: - $ bin/ejabberdctl status - The node ejabberd@localhost is started with status: started - ejabberd 2.1.8 is running in that node + $ bin/mongooseimctl status + The node mongooseim@localhost is started with status: started + MongooseIM version 1.3.1 is running on that node 4. Building the testing target and running tests.