Murk1108 / pygowave forked from p2k/pygowave

Federation support in pygowave

The current state of federation in short: It's unfinished and does not work.

That said, it's on a good way:

ToDo list and other things

    - Actually apply received data to the local database
    - Switch to the pygowave rpc
    - Better integration of protocol buffers into the ORM


Setting up Federation support:

    Federation support is (like in google's fedone) implemented as an xmpp component (see XEP-0114), but
    since recent development makes pygowave more independent from other software, it might eventually bring
    it's own xmpp server. That however won't happen before version 2.

    Dependencies:

        Apart from dependencies on twisted, you need:
            - m2crypto
            - pyasn1 0.0.9a

    1. Configure your jabber server

        If you have an ejabberd server like me, add the following lines to ejabberd.cfg:

        {5275, ejabberd_service, [{host, "wave.YOUR-DOMAIN.TLD",
                                 [{password, "SOMEPASSWORD"}]}]},

        Note: This makes it possible to run the component on a different server than your jabber server.

    2. Configure pygowave

        In the settings.py file, add/edit the following lines to suit the values you chose above

            XMPP_ID = "wave.YOUR-DOMAIN.TLD"
            XMPP_PASSWORD = "SOMEPASSWORD"
            XMPP_PORT = 5275
            XMPP_HOST = "localhost"

            CERTIFICATE_FILE = '/tmp/cert.pem'
            CERTIFICATE_KEY_FILE = '/tmp/cert.key'

    3. Put your SSL certificate in pem format and the corresponding RSA key into the place
       you specified in the settings file

    4. Run the component

        To start the server and let it run in the foreground:

            twistd -ny pygowave-xmpp.tac

        Run this instead of the pygowave-rpc.tac file!