#### Tutorials

* [XMPP Frontend](frontends/xmpp.html)

   * [Spectrum 2 in gateway mode](tutorials/gateway_mode.html)

#### Configuration

* [Configuration file description](configuration/config_file.html)

* [MySQL Support](configuration/mysql.html)

* [PostgreSQL Support](configuration/postgresql.html)

* [Logging](configuration/logging.html)

#### Management

* [spectrum2_manager tool](management/spectrum2_manager.html)

* [Web Interface](management/web_interface.html)

* [Getting a backtrace](management/getting_backtrace.html)

* [Munin integration](management/munin.html)

#### Development

* [Spectrum 2 architecture](development/architecture.html)

* [Writing backend in any language (or How the backend works inside)](development/protocol.html)

### Third-party plugins

Spectrum 2 should work with any third-party libpurple plugin which is properly installed. For example, popular plugins:

Protocol variable| website | Description

-----------------|------------

prpl-facebook| [https://github.com/jgeboski/purple-facebook](website) | Facebook

prpl-telegram| [https://github.com/majn/telegram-purple](website) | Telegram

prpl-skypeweb| [https://github.com/EionRobb/skype4pidgin/tree/master/skypeweb](website) | Skype

These plugins are included by default in our Docker image.

### Setting libpurple plugins configurations

Some libpurple protocol plugins allow setting configuration variables. Spectrum 2 passes every variable set in `purple` section to libpurple library. If you need to set such options, you can do it for example like this in your configuration file:

	[purple]

	clientlogin=1

	ssl=0

>

> * [admin_jid](#serviceadminjid)

> * [admin_password](#serviceadminpassword)

> * [backend](#servicebackend)

> * [backend_host](#servicebackendhost)

> * [backend_port](#servicebackendport)

> * [group](#servicegroup)

> * [jid](#servicejid)

> * [password](#servicepassword)

> * [pidfile](#servicepidfile)

> * [user](#serviceuser)

> * [users_per_backend](#servicusersperbackend)

> * [working_dir](#serviceworkingdir)

### Types of configuration fields

Following types are used:

integer - Examples: key=0

string - Examples: key=something

boolean - Examples: key=0 or key=1

list - List of strings (or Jabber IDs). You can specify this options more than once:

as if you have more backends running for the same user-base. Also, if there is some problem with single backend, it will affects only users

connected using this particular backend, so it is good idea to have more backends running. However, the more backends you have

the more processes the machine has and since some point, it will become less useful. There is also some memory overhead, so if you run

500 users on single backend, it will take little bit less memory than 500 users on 5 backends (but it is not significant unless you decide

to have hundreds of backends).

If you presume to have just few users on your personal server, it can be useful to configure `service.users_per_backend=1`. Ever user will

get his own separated backend process.

For bigger user-base, you have to increase the `service.users_per_backend` value, but there is no optimal value to be suggested yet.

#### service.working_dir

Key | val

----|----

Description:|Configures path to directory when Spectrum 2 stores its data files.

Context:|server-mode and gateway-mode

Type:|string

Default:|/var/lib/spectrum2/$jid

This option configures path to directory when Spectrum 2 stores its data files like for example SQLite3 database.