|
|
|
@ -216,7 +216,7 @@ comments for a relative URL to support HTTP, HTTPS and even domain transfers
|
|
|
|
|
without manual intervention. But you can chain Isso to support multiple
|
|
|
|
|
websites on different domains.
|
|
|
|
|
|
|
|
|
|
The following example uses [gunicorn](http://gunicorn.org/) as WSGI server (you
|
|
|
|
|
The following example uses `gunicorn <http://gunicorn.org/>`_ as WSGI server (you
|
|
|
|
|
can use uWSGI as well). It is *not* possible to run the isso executable for
|
|
|
|
|
multiple sites.
|
|
|
|
|
|
|
|
|
@ -228,10 +228,16 @@ Let's say you maintain two websites, like foo.example and other.foo:
|
|
|
|
|
[general]
|
|
|
|
|
host = http://foo.example/
|
|
|
|
|
dbpath = /var/lib/isso/foo.example.db
|
|
|
|
|
|
|
|
|
|
$ cat /etc/isso.d/other.foo.cfg
|
|
|
|
|
[general]
|
|
|
|
|
host = http://other.foo/
|
|
|
|
|
dbpath = /var/lib/isso/other.foo.db
|
|
|
|
|
|
|
|
|
|
Then you run Isso with gunicorn like this:
|
|
|
|
|
|
|
|
|
|
.. code-block:: bash
|
|
|
|
|
|
|
|
|
|
$ export ISSO_SETTINGS="/etc/isso.d/foo.example.cfg;/etc/isso.d/other.foo.cfg"
|
|
|
|
|
$ gunicorn isso.dispatch -b localhost:8080
|
|
|
|
|
|
|
|
|
|