From diaspora* project wiki
Revision as of 12:53, 30 September 2014 by Zauberstuhl (talk | contribs) (→‎Run it)
Work in progressWork in progress:This article is a work in progress, it may contain incomplete or inaccurate information. There may be additional information on the talk page.
NoteNote:Report issues and suggestions to the Vines server at
NoteNote:The pull request integrating this with Diaspora is at

This wiki-page is about setting up Vines on your Diaspora installation.

Vines is an XMPP chat server that connects you with large clusters of machines as easily as chatting with a friend.
It's a new, simpler way to manage your servers in the cloud or the data center.


Set up branch

Checkout or merge XMPP chat feature branch from zauberstuhl/diaspora.git:

 git remote add zauberstuhl
 git fetch zauberstuhl && git checkout -b xmpp_chat_feature zauberstuhl/xmpp_chat_feature
WarningWarning:xmpp_chat_feature-branch is based upon Diaspora develop-branch!


All required dependencies are included in your Gemfile. The only thing you have to do now is follow the Update guide! In short, execute following:

 export RAILS_ENV=development
 bundle install
 bundle exec rake db:migrate


You'll find all required configuration parameters in diaspora.yml.example. If you'd like to activate the chat feature you have to copy paste the chat section from diaspora.yml.example to your actual diaspora.yml configuration file and activate the chat globally:

    enabled: true

If you have already a working XMPP server and need only the front-end:

    enabled: true
      enabled: false

It is also possible to configure the port and address of the client-to-server, server-to-server and the BOSH service. You'll also find the required parameters in diaspora.yml.example with a small description.


WarningWarning:For encrypted communication we need a cerificate and the related key.

Put your files in the vines-cert folder, you can configure the path in diaspora.yml under the chat section.

The default path is /path_to_diaspora_installation/config/vines/.
Also the domain name should be included in the file name e.g.:


If you have no certificate and want to generate a self-signed you can do that with vines, too. Just execute in you diaspora environment bundle exec vines cert and you should be good to go ..

NoteNote:If you use your server in a development mode, think about enabling acceptance of self-signed certificates in your diaspora.yml!

Run it

If you are finished configuring the chat server you can start Diaspora as normal:


Log into Diaspora and you should see the web client in the right corner. You can also log into it with your favorite desktop client like Pidgin.

For that use your Diaspora ID and your Diaspora password.


I received a warning on startup!?

You enabled the chat feature but haven't configured BOSH! That
could lead to mixed-content problems with the http clients. Please
think about editing your proxy configuration as described in:


The internal xmpp server does not support https and
even if we implement it, we would ran into certificate issues.
The problem with mixed-content is described here:

The easiest way of avoiding certificate and mixed-content issues is to use a proxy (see apache and nginx section below)!

If you finished configuring your proxy settings you also have to adjust diaspora.yml!
For my examples below, it would look like this:

        proxy: true
        bind: '/http-bind'


RewriteEngine On
RewriteCond %{REQUEST_URI} ^/http-bind
RewriteRule ^/(http\-bind.*)$ balancer://chat%{REQUEST_URI} [P,QSA,L]
RewriteRule ^/(.*)$ balancer://diaspora%{REQUEST_URI} [P,QSA,L]
<Proxy balancer://diaspora>
<Proxy balancer://chat>


This is NOT tested. Please let me know if there are any problems with the configuration settings!

upstream chat_cluster {
  server localhost:5280;
location /http-bind {
  proxy_set_header X-Real-IP $remote_addr;
  proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
  proxy_set_header Host $http_host;
  proxy_set_header X-Forwarded-Proto https;
  proxy_redirect off;
  client_max_body_size 4M;
  client_body_buffer_size 128K;
  proxy_pass http://chat_cluster;


On default Vines will log to log/vines.log and has a log level of info set. Set the logging level to debug, info, warn, error, or fatal. The debug level logs all XML sent and received by the server.

        file: 'log/vines.log'
        level: 'debug'