Frequently asked questions

Can Convos be extended and customized?

Yes. Convos supports plugins, but there have not yet been any plugins
developed. We hope to implement
#244 and
#90 as the first core
plugins.

Look at the configuration guide to see which configuration
parameters that have to be set to load a plugin.

Can Convos run behind behind my favorite web server?

Yes, but Convos and the web server needs to be configured properly and
WebSockets need to be supported through the
chain.

The first thing is that the environment variable
MOJO_REVERSE_PROXY must be set to a
true value.

The other thing is that the reverse proxy need to pass on some HTTP headers to
Convos, so correct URLs will be generated. Below are two examples for
setting up Convos behind nginx or Apache. Here are the important headers:

“Host” header must be set to the original request’s “Host” header.

“X-Forwarded-Proto” header must be set to either “http” or “https”.

“X-Request-Base” header must be set if your application is not available
from the root of your domain.

Here is a complete example on how to start Convos, and configur either nginx
or Apache:

Why can’t Convos do X?

In most of the cases it’s either because we haven’t thought about it or
haven’t had time to implement it yet. It might also be because we do not want
to implement certain features. We do not want Convos to support every weird
feature, since we want both the user experience and code base to be clean.