GithubHelp home page GithubHelp logo

edwardt / ejabberd-modules Goto Github PK

View Code? Open in Web Editor NEW

This project forked from medigram/ejabberd-modules

0.0 3.0 0.0 14.23 MB

Tracking repo for https://svn.process-one.net/ejabberd-modules/

Home Page: https://svn.process-one.net/ejabberd-modules/

Shell 0.39% Erlang 77.00% C 0.54% C++ 0.14% Objective-C 0.27% Perl 3.21% PHP 14.78% CSS 0.43% JavaScript 2.34% Python 0.11% Java 0.79%

ejabberd-modules's Introduction

ejabberd-modules is a collaborative development area for ejabberd
modules developers and users.


    For users
    =========

You need to have Erlang installed.

To use an ejabberd module coming from this repository:

- Read the module specific README to see if special steps are needed
  to deploy it.

- Run "./build.sh" or "build.bat" in the root (usually trunk
  directory) of the wanted 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 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 file make.beam
In Debian and other distributions you can try to install packages like:
  erlang-dev erlang-nox erlang-tools


    For developers
    ==============

The following organisation has been set-up for the development:

- Each module has its own SVN structure (trunk/branches/tags) to allow
  independent versioning.

- Development and compilation of module should be possible without
  ejabberd SVN, as long as developers check-out the ejabberd-dev
  module. This module contains include file 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 works on Windows)
 doc/: Documentation dir
 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: *nix build script.
 build.bat: Windows build script.

- Module developers should put in the README if the module has
  requirements or known incompatibilities with other modules (for
  example, by modifying the same main ejabberd modules).

ejabberd-modules's People

Watchers

edwardt avatar James Cloos avatar  avatar

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.