use/httpserver.rst: multiple updates

* Update config variables
    * add favicon
    * host is nowadays known as hosts4
    * add hosts6
    * move keepalive above port as that is how it appears in the bot too
    * specify that HTTPd might require port change, not HTTP
    * HTTPd might not work if port is too low = port is under 1024
* Apache is in front of Supybot's HTTPd, not behind.
This commit is contained in:
Mikaela Suomalainen 2014-07-27 15:03:12 +03:00
parent 05abf551d4
commit 625d6939ce

View File

@ -7,14 +7,19 @@ Configuration
The HTTP comes with a couple of additional variables: The HTTP comes with a couple of additional variables:
* :ref:`supybot.servers.http.host`: The host the bot will bind. In most of * :ref:`supybot.servers.http.favicon`: Path to the file which is shown to
the cases, you will use 0.0.0.0 (everything) or 127.0.0.1 (restricted to browsers as favicon.
local connections). Defaults to 0.0.0.0 * :ref:`supybot.servers.http.hosts4`: The IPv4 addresses where the bot
* :ref:`supybot.servers.http.port`: The port the bot will bind. May not work will bind. In most of the cases, you will use 0.0.0.0 (everything) or
if the number is too low. Defaults to 8080 (alternative HTTP port). 127.0.0.1 (restricted to local connections). Defaults to 0.0.0.0
* :ref:`supybot.servers.http.hosts6`: The IPv6 addresses where the bot
will bind. Defaults to empty.
* :ref:`supybot.servers.http.keepAlive`: Determines weather the HTTP server * :ref:`supybot.servers.http.keepAlive`: Determines weather the HTTP server
will run even if has nothing to serve. Defaults to False, because the HTTP will run even if has nothing to serve. Defaults to False, because the
might require to change the port, if it is already taken. HTTPd might require to change the port, if it is already taken.
* :ref:`supybot.servers.http.port`: The port the bot will bind. May not
work if the number is below 1024. Defaults to 8080 (alternative HTTP port).
Using the server Using the server
================ ================
@ -22,9 +27,10 @@ Using the server
At the root of the server, you will find a list of the plugins that have a Web At the root of the server, you will find a list of the plugins that have a Web
interface, and a link to them. Each plugin has its own subdirectory(ies). interface, and a link to them. Each plugin has its own subdirectory(ies).
You may also want to have Apache behind Supybot's HTTP server, if you want to You may also want to have Apache in front of Supybot's HTTP server, if
use subdomains. Here is an example of configuration (I didn't test it with the you want to use subdomains. Here is an example of configuration
rewrite, please notify me whether it works or not): (I didn't test it with the rewrite, please notify me whether it works or
not):
.. code-block:: apache .. code-block:: apache