Recoll WebUI can be used as a standalone application or through a web server via WSGI/CGI. Regardless of the mode of operation you need Recoll to be configured on your system as the WebUI only provides a front-end for searching and does not handle index configuration etc.

The standalone application can be configured to run automatically using systemd. See the file README.systemd.

There's some optional command-line arguments available:

Run as WSGI/CGI

See the following link for a complete run-through:

https://www.lesbonscomptes.com/recoll/pages/recoll-webui-install-wsgi.html

Example WSGI/Apache2 config:

WSGIDaemonProcess recoll user=recoll group=recoll threads=5 display-name=%{GROUP} python-path=/var/recoll-webui-master WSGIScriptAlias /recoll /var/recoll-webui-master/webui-wsgi.py <Directory /var/recoll-webui-master> WSGIProcessGroup recoll Order allow,deny allow from all </Directory>

Remarks: * Without "python-path=" you might see errors that it can't import webui * Run the WSGIDeamonProcess run under the username (user=xyz) of the user that you want to have exposed via web

Example Upstart-Script for Ubuntu to run the indexer as daemon:

description "recoll indexer" start on runlevel [2345] stop on runlevel [!2345] respawn pre-start script exec sudo -u recoll sh -c "/usr/local/share/recoll/examples/rclmon.sh start" end script pre-stop script exec sudo -u recoll sh -c "/usr/local/share/recoll/examples/rclmon.sh stop" end script

Remarks: * You need to configure the user for which the indexer should run ("sudo -u [myuser])

Example Crontab entry to have the indexer at least once a day:

22 5 * * * recoll recollindex